Register Regis and HolographMe projection agents

[mdheller]

Purpose

Register the agents that operate the HolographMe → Regis Semantic Feature Plane bridge.

Upstream anchors

• SocioProphet/gaia-world-model#19
• SocioProphet/HolographMe#10
• SocioProphet/prophet-core-contracts#2
• SocioProphet/prophet-core-policy#1

Agents to register

1. holographme-projection-exporter
2. regis-feature-assertion-builder
3. regis-embedding-card-writer
4. regis-domain-gate-evaluator
5. regis-purpose-compatibility-evaluator
6. regis-authority-band-evaluator
7. regis-promotion-reviewer
8. regis-revocation-propagator
9. regis-denied-field-leakage-auditor
10. regis-retention-enforcer

Required registration fields

Each agent registration should declare:

• agent id;
• owner repo;
• allowed input contracts;
• allowed output contracts;
• authority band;
• permitted actions;
• prohibited actions;
• policy gates required before execution;
• audit / receipt obligations;
• revocation behavior;
• failure classification;
• human review requirements.

Non-negotiable boundaries

• No agent reads raw twin state unless operating inside HolographMe with proper consent and runtime authority.
• Regis agents consume only consent-scoped projection artifacts.
• No agent promotes features to canonical state without a PromotionDecision.
• No agent may transform denied field values into features, embeddings, or inferred absence signals.

Acceptance criteria

• All bridge agents are registered with bounded authority.
• Each agent points to the relevant contract and policy gates.
• Revocation propagation and denied-field leakage audit are explicit agent responsibilities.