Regis ingest conformance worksheet for TwinProjectionFeature and admission spine v0.1

[mdheller]

Purpose

Define the Regis-side conformance checklist for ingesting consent-scoped HolographMe projection features and later materializing them through the v0.1 admission spine.

This is the consumer-side mirror of the HolographMe exporter conformance work.

Gate: do not implement before contracts are tagged

Do not implement runtime ingest against draft contracts.

Begin implementation only after the relevant prophet-core-contracts contracts are merged and pinned:

• TwinProjectionFeature.v0.1 for feature ingestion;
• PolicyRequest.v0.1 / PolicyDecision.v0.1 for policy decision binding;
• AdmissionToken.v0.1 binding to canonical PolicyDecision for materialization;
• Effect.v0.1 stub for admission-chain integration fixtures;
• AuditRecord.v0.1 for durable audit output, when available.

Until then, this issue is a worksheet and acceptance target only.

Regis boundary

Regis may ingest governed feature records and admitted graph deltas.

Regis must not ingest or store:

• raw HolographMe twin state;
• denied projection fields;
• forbidden fields;
• unrestricted raw transcripts;
• similarity-only identity merges;
• canonical truth mutations without admission.

Phase A: TwinProjectionFeature ingest conformance

Input: canonical TwinProjectionFeature.v0.1 examples from prophet-core-contracts.

Acceptance checks:

1. Regis validates every incoming feature against the pinned schema.
2. Regis rejects records with raw_twin_payload_present=true.
3. Regis rejects records with unknown feature_family.
4. Regis rejects records with unsafe source_field_reason.
5. Regis recomputes or verifies content_hash.
6. Regis verifies lineage_hash.
7. Regis preserves do_not_learn=true.
8. Regis preserves do_not_link=true.
9. Regis preserves revocation_state and policy_state.
10. Regis applies active/allowed records only to non-canonical feature surfaces unless separately admitted.
11. Regis blocks or restricts revoked/expired records.
12. Regis emits a graph-delta fixture without raw twin state.

Phase B: admission-token gated materialization

Input: TwinProjectionFeature plus an admitted Operation Plane token.

Acceptance checks:

1. Schema-valid feature alone is not sufficient for canonical graph materialization.
2. Materialization requires a valid AdmissionToken.
3. Token action/resource/authority must cover the requested graph operation.
4. Token risk tier must match the source PolicyDecision once PolicyDecision binding lands.
5. Token restrictions must be preserved in graph metadata.
6. DoNotLearn prevents embedding/model/memory sink activation.
7. DoNotLink prevents cross-domain identity linking and alias merge.
8. NoSimilarityAuthority prevents similarity-only canonical mutation.
9. Missing/expired/consumed/invalid token rejects the graph operation.
10. Rejected operations produce failure fixtures, not partial graph state.

Phase C: negative fixtures

Add Regis ingest fixtures for:

• raw twin payload leakage;
• denied field emitted;
• unsafe reason string;
• null feature value;
• bad content hash;
• bad lineage hash;
• expired consent still allowed;
• revoked feature still allowed;
• DoNotLearn dropped;
• DoNotLink dropped;
• schema-valid feature without AdmissionToken attempting canonical materialization;
• invalid AdmissionToken attempting materialization;
• similarity-only merge attempt;
• DoNotLink merge attempt;
• agent direct canonical truth write.

Each negative fixture must declare a stable expected_failure code and validators must require that code to appear in the computed failure-code set.

Phase D: audit and receipts

Once AuditRecord.v0.1 lands:

1. Accepted materialization writes an audit record.
2. Rejected materialization writes an audit record with admission_outcome=rejected and execution_outcome=not_attempted.
3. Failed materialization writes admission_outcome=accepted and execution_outcome=failed.
4. Rollback writes a new immutable audit record referencing the prior record/effect.
5. Audit records preserve risk tier, restrictions, verification result, and effect reference.

Non-goals

• No raw twin storage.
• No production revocation-index implementation in v0.1.
• No similarity-authorized canonical merge.
• No embedding generation unless a future admitted override exists.
• No runtime execution beyond static conformance fixtures until contracts are tagged.

Suggested implementation shape

• Add tools/validate_regis_ingest_examples.py or extend the existing Regis validator.
• Place fixtures under examples/regis/ingest/ or tests/fixtures/regis/ingest/.
• Keep positive and negative fixtures separate.
• Wire validation into make validate.
• Cross-link the pinned prophet-core-contracts release/tag in the README or conformance doc.

Dependencies

• prophet-core-contracts#8 for TwinProjectionFeature.v0.1.
• prophet-core-contracts#10 for PolicyRequest / PolicyDecision.v0.1.
• AdmissionToken binding tranche for canonical materialization gates.
• prophet-core-contracts#12 / AuditRecord work for durable audit output.