Execution plan: ground ontology alignment lessons into cskg.vnext and boundary profiles

[mdheller]

Purpose

Track the implementation plan for converting the Drive-folder ontology-alignment / KBP / grounded-reading lessons into repo artifacts and executable validation. This follows the inventory and lesson ledgers added on 2026-05-10 and links to the existing cskg.vnext and boundary-admission work.

Objective

Move from research grounding to implementation substrate:

paper lesson
-> typed record/schema
-> boundary watcher rule
-> golden fixture
-> negative fixture
-> implementation helper
-> validation receipt
-> cross-repo adoption plan

Tranche plan

T1 — Spec expansion

Target file:

• spec/drafts/cskg_vnext_profile.md

Add first-class record definitions:

• EvidenceContextRecord
• AlignmentCandidateRecord
• ConceptLinkCandidate
• ModuleBoundaryRecord
• MatcherRunReceipt
• OutlierAuditRecord
• PipelineRunReceipt
• EDLReceipt
• StructuredSourceMergeReceipt
• AttributeValidationReceipt
• DynamicsManifest
• FeedbackReviewRecord

Acceptance criteria:

• records have required/optional field classification;
• record lifecycle is mapped to Beacon-A/B/C and BoundaryReceipt;
• each record includes claim/evidence/admission state;
• identity and privacy labels are explicit where applicable.

T2 — Annex X boundary semantics

Target file:

• spec/drafts/annex_x_boundary_admission_profile.md

Add:

• BoundaryWatcherDecision
• BoundaryReceipt
• BoundaryStateMachine
• FailClosedCompositionPolicy
• BoundaryNegativeTestVector

Acceptance criteria:

• no path bypasses classification, validation, and receipt;
• fallback cannot mean fail-open;
• watcher timeouts deny/quarantine;
• DoNotLearn and DoNotLink are defaulted for unknown identity risk;
• proof-program and worldlet examples are included.

T3 — Golden and negative fixture set

Add fixture targets for:

Positive:

• public ConceptNet-style IsA edge;
• WordNet/ontology PartOf edge;
• Socrates binary context evidence;
• Socrates unary context evidence;
• Socrates composite TOD evidence;
• locality module with coverage receipt;
• RTFM-style DynamicsManifest.

Negative:

• embedding-near SameAs human identity link;
• unary-derived contact relation;
• uncertain concept link without review;
• ontology module without coverage receipt;
• worldlet action without dynamics manifest;
• semantic-memory promotion without PromotionRule receipt;
• vectorization/training on unclassified sentence text.

Acceptance criteria:

• every negative fixture fails closed;
• every positive fixture emits a receipt;
• fixture names encode expected decision state.

T4 — Experimental reference implementation

Target package:

• reference/experimental/tritrpc_requirements_impl_v4/

Add candidate modules:

• boundary.py
• cskg.py
• memory.py
• identity_prime.py

Acceptance criteria:

• canonical encode/decode helpers for new records;
• deterministic canonicalization for CSKG array/list fields;
• watcher composition function;
• fail-closed state transitions;
• tests for fixtures.

T5 — Cross-repo adoption issues

Create downstream issues for:

• SocioProphet/ontogenesis: schema generation and ontology/module objects;
• SocioProphet/holmes: concept-link and formalization candidates;
• SocioProphet/sherlock-search: evidence retrieval and context records;
• SocioProphet/guardrail-fabric: watcher policy and fail-closed defaults;
• SocioProphet/sociosphere: registry/admission dashboard and memory release ledger.

Acceptance criteria:

• issues reference TriTRPC profile paths;
• each downstream issue has acceptance tests;
• no repo claims ownership of another repo’s boundary.

T6 — Proof/evidence doctrine hardening

Add a compact doctrine note connecting Gödelization, CSKG, FSMS, and boundary admission.

Acceptance criteria:

• explicit distinction: candidate / evidence / admitted / promoted / theorem;
• SameAs and entity resolution treated as proof obligations;
• mathematical proof-program analogue included.

Estimated turn count

Chat-driven implementation estimate: 8 turns total, assuming connector write access remains available and no large CI failures block us.

1. Spec expansion for records.
2. Annex X boundary profile draft.
3. Fixture design and JSON/YAML examples.
4. Experimental reference implementation scaffolding.
5. Test suite for fail-closed behavior.
6. Cross-repo issue fan-out.
7. Review pass and gap audit.
8. Stabilization pass: tighten names, non-goals, acceptance criteria, and validation commands.

If we keep the work docs-only/spec-only, it can be done in about 4 turns. If we include reference code and tests, use 8 turns. If we require PRs, CI, and downstream cross-repo adoption, expect 10-12 turns.

Non-goals

• Do not implement a production ontology matcher in TriTRPC.
• Do not make CSKG relation semantics part of Braid243.
• Do not admit identity/SameAs edges without Identity-Prime controls.
• Do not permit direct semantic-memory promotion from parser/model output.
• Do not replace stable v1.

[mdheller]

Braided cadence, risk, and attestation alignment

This comment adds the missing control dimension to the execution plan: the system must align semantic cadence across braided layers according to risk, and every escalation must be attestable.

The core issue is not just which records exist. It is when meaning is sent, inherited, refreshed, committed, quarantined, or promoted. TriTRPC vNext already separates hot-path coordinates, semantic braid/state, beacons, stream inheritance, and commit receipts. cskg.vnext needs to bind those layers to risk and attestation.

Design law

Send the smallest meaning-bearing object at the slowest cadence that still satisfies correctness, safety, privacy, and audit.

Increase cadence only when freshness risk demands it.
Increase attestation only when consequence risk demands it.
Never lower either because a model, matcher, or agent is confident.

Braided cadence layers

C0 — Hot frame cadence

Used for high-frequency operational frames.

Examples:

• route handle;
• compact CTRL243;
• short State243 posture;
• stream data segment;
• canonical payload digest;
• no raw relation labels unless payload requires them.

Allowed when risk is low or context has already been beaconed and pinned.

C1 — Stream inheritance cadence

Used when many frames share route, schema, context, policy, vocabulary, or memory defaults.

Examples:

• BulkPutEdges stream;
• repeated sensor readings;
• graph scan pages;
• proof diagnostic stream;
• worldlet observation stream.

Required when repeating semantic fields per-frame would add ambiguity or overhead.

C2 — Beacon-A capability cadence

Used for capability, dictionary, schema, suite, watcher, vocabulary, and policy publication.

Examples:

• route dictionary;
• schema hash;
• vocabulary hash;
• watcher bundle handle;
• policy epoch;
• privacy default;
• degradation mode.

Required before any handled route, watcher, or profile is trusted.

C3 — Beacon-B intent / lease cadence

Used for provisional acts, reservations, action leases, write attempts, promotion attempts, and proof-publication intent.

Examples:

• put edge intent;
• semantic-memory promotion intent;
• SameAs resolution intent;
• worldlet action intent;
• proof diagnostic publication intent;
• required receipt class.

Required before consequence-bearing actions.

C4 — Beacon-C commit / receipt cadence

Used for commit, tombstone, denial, quarantine, rollback, evidence promotion, or memory release.

Examples:

• BoundaryReceipt;
• SemanticMemoryRelease receipt;
• SameAs quarantine receipt;
• proof diagnostic admission receipt;
• action self-perception receipt;
• policy denial receipt.

Required before anything becomes admitted state.

C5 — Release / audit cadence

Used for slow, durable, externally meaningful releases.

Examples:

• dataset release;
• vocabulary release;
• policy bundle release;
• watcher bundle release;
• semantic memory release;
• proof/evidence release;
• attestation report.

Required for reproducibility, governance, and downstream trust.

Risk tiers

R0 — Public / non-consequential

Examples: public documentation, public concepts, non-sensitive read-only lookup.

Minimum cadence:

• C0/C1 allowed.
• C2 if using handles or inherited context.
• C4 optional unless persisted.

Minimum attestation:

• canonical encoding check;
• schema hash where applicable.

R1 — Internal / operational

Examples: internal graph query, repo metadata, non-sensitive route scan.

Minimum cadence:

• C1 stream inheritance;
• C2 capability/context beacon;
• C4 receipt if persisted.

Minimum attestation:

• schema + source + policy epoch.

R2 — Memory-bearing / knowledge candidate

Examples: CSKG candidate edge, ontology alignment candidate, implicit relation candidate, module boundary candidate.

Minimum cadence:

• C2 context/schema/vocabulary beacon;
• C4 BoundaryReceipt before admission;
• C5 if promoted to semantic memory.

Minimum attestation:

• evidence context;
• matcher/extractor/version receipt;
• claim mode;
• promotion rule if memory write occurs.

R3 — Identity / quasi-identifier / linkage risk

Examples: SameAs, person/account/org/contact/location linkage, source-specific identity merge, behavioral basis vectors.

Minimum cadence:

• C2 Identity-Prime policy and privacy defaults;
• C3 explicit linkage intent;
• C4 quarantine or admission receipt;
• C5 audit report for durable promotion.

Minimum attestation:

• DoNotLearn and DoNotLink default;
• capability;
• provenance;
• identity proof/review artifact;
• non-linkability decision.

R4 — Actuation / security / proof-facing consequence

Examples: worldlet actuation, runtime admission, proof diagnostic publication, finite spectrum report, policy decision, build admission.

Minimum cadence:

• C2 capability/policy/watcher bundle;
• C3 action or publication lease;
• C4 commit/denial receipt;
• C5 release/audit if durable.

Minimum attestation:

• watcher composition receipt;
• source/provenance check;
• action bounds;
• self-perception or equivalent external evidence for physical actions;
• proof/regression receipt for theorem-adjacent outputs.

R5 — Secret / critical / irreversible

Examples: credentials, raw PII/PHI, critical system maps, incident-response details, irreversible actuation, training contamination.

Minimum cadence:

• C2 high-assurance policy and capability;
• C3 explicit break-glass or approved workflow intent;
• C4 mandatory denial/quarantine/admission receipt;
• C5 independent audit and retention/tombstone record.

Minimum attestation:

• no silent processing;
• no fallback to permissive route;
• vault reference instead of raw payload;
• dual control or explicit governance path when applicable;
• DoNotLearn/DoNotLink unless specifically overridden by policy.

Attestation objects

Add or align these records:

CadenceBinding {
  cadence_class,
  frame_kind,
  stream_scope,
  beacon_epoch,
  inherited_context_refs[],
  refresh_rule,
  expiry_rule
}

RiskAssessment {
  risk_tier,
  risk_labels[],
  identity_risk,
  memory_risk,
  action_risk,
  proof_risk,
  privacy_risk,
  consequence_summary
}

AttestationRequirement {
  required_watchers[],
  required_receipts[],
  required_policy_refs[],
  required_evidence_refs[],
  fallback_policy,
  degraded_mode_policy
}

AttestationReceipt {
  input_hash,
  output_hash,
  cadence_binding_hash,
  risk_assessment_hash,
  watcher_decision_hashes[],
  policy_hashes[],
  evidence_hashes[],
  final_decision,
  retention_action
}

Pattern cadence by artifact family

CSKG edge ingest

• Public edge: C1 stream + C2 schema/vocabulary + C4 edge receipt.
• Implicit relation edge: C2 extractor/matcher context + C4 evidence receipt + no semantic promotion without C5.
• SameAs/human linkage: C2 Identity-Prime + C3 linkage intent + C4 quarantine/admit receipt + C5 audit before semantic release.

FSMS memory

• Working memory: C1/C2 with TTL.
• Episode bundle: C4 per episode/trace.
• Semantic memory release: C5 only after promotion rule receipt.
• Forgetting/tombstone: C4 event + C5 release/audit when durable.

Minimal Universe / worldlet

• Sensor trace: C0/C1 sampled frame; C4 before admitted observation.
• Action attempt: C3 intent/lease; C4 commit only after echo/self-perception.
• Dynamics document: C2/C5 DynamicsManifest depending on reuse scope.
• Learned policy update: R4/R5 depending on data; requires C5 attestation.

Proof programme

• Diagnostic computation: C2 context + C4 computation receipt.
• Theorem-adjacent claim: C3 publication intent + C4 proof/regression receipt.
• Release: C5 with non-claim box and validation commands.
• Missing regression/provenance: error/quarantine, never promotion.

Implementation requirement

Add cadence/risk/attestation validation before implementing arbitrary watcher middleware.

Proposed modules:

boundary.py
  BoundaryWatcherDecision
  BoundaryReceipt
  FailClosedCompositionPolicy

cadence.py
  CadenceBinding
  CadenceClass
  RefreshRule
  ExpiryRule

risk.py
  RiskTier
  RiskAssessment
  AttestationRequirement

attestation.py
  AttestationReceipt
  validate_attestation_requirements()

Negative tests

• R3 identity edge sent only as C0 hot frame -> reject.
• R4 action without Beacon-B lease -> reject.
• R4 action with no Beacon-C echo receipt -> attempted_not_admitted.
• R2 candidate edge promoted to semantic memory without C5 release receipt -> reject.
• R5 raw credential in payload instead of vault reference -> quarantine.
• R2 implicit relation missing evidence context -> quarantine.
• R4 finite spectrum report missing regression receipt -> reject.
• fallback flag permits action route without explicit route policy -> reject.

Acceptance criteria addition for #69

• Add cadence/risk/attestation matrix to cskg.vnext or Annex X.
• Define CadenceBinding, RiskAssessment, AttestationRequirement, and AttestationReceipt.
• Add tests proving risk tier controls cadence and attestation requirements.
• Add examples for CSKG, FSMS, Minimal Universe, and proof programme.
• Ensure fallback/degraded mode cannot reduce attestation requirements.

[mdheller]

Braided cadence, risk, and attestation alignment

This comment adds the missing control dimension to the execution plan: the system must align semantic cadence across braided layers according to risk, and every escalation must be attestable.

The core issue is not just which records exist. It is when meaning is sent, inherited, refreshed, committed, quarantined, or promoted. TriTRPC vNext already separates hot-path coordinates, semantic braid/state, beacons, stream inheritance, and commit receipts. cskg.vnext needs to bind those layers to risk and attestation.

Design law

Send the smallest meaning-bearing object at the slowest cadence that still satisfies correctness, safety, privacy, and audit.

Increase cadence only when freshness risk demands it.
Increase attestation only when consequence risk demands it.
Never lower either because a model, matcher, or agent is confident.

Braided cadence layers

C0 — Hot frame cadence

Used for high-frequency operational frames.

Examples:

• route handle;
• compact CTRL243;
• short State243 posture;
• stream data segment;
• canonical payload digest;
• no raw relation labels unless payload requires them.

Allowed when risk is low or context has already been beaconed and pinned.

C1 — Stream inheritance cadence

Used when many frames share route, schema, context, policy, vocabulary, or memory defaults.

Examples:

• BulkPutEdges stream;
• repeated sensor readings;
• graph scan pages;
• proof diagnostic stream;
• worldlet observation stream.

Required when repeating semantic fields per-frame would add ambiguity or overhead.

C2 — Beacon-A capability cadence

Used for capability, dictionary, schema, suite, watcher, vocabulary, and policy publication.

Examples:

• route dictionary;
• schema hash;
• vocabulary hash;
• watcher bundle handle;
• policy epoch;
• privacy default;
• degradation mode.

Required before any handled route, watcher, or profile is trusted.

C3 — Beacon-B intent / lease cadence

Used for provisional acts, reservations, action leases, write attempts, promotion attempts, and proof-publication intent.

Examples:

• put edge intent;
• semantic-memory promotion intent;
• SameAs resolution intent;
• worldlet action intent;
• proof diagnostic publication intent;
• required receipt class.

Required before consequence-bearing actions.

C4 — Beacon-C commit / receipt cadence

Used for commit, tombstone, denial, quarantine, rollback, evidence promotion, or memory release.

Examples:

• BoundaryReceipt;
• SemanticMemoryRelease receipt;
• SameAs quarantine receipt;
• proof diagnostic admission receipt;
• action self-perception receipt;
• policy denial receipt.

Required before anything becomes admitted state.

C5 — Release / audit cadence

Used for slow, durable, externally meaningful releases.

Examples:

• dataset release;
• vocabulary release;
• policy bundle release;
• watcher bundle release;
• semantic memory release;
• proof/evidence release;
• attestation report.

Required for reproducibility, governance, and downstream trust.

Risk tiers

R0 — Public / non-consequential

Examples: public documentation, public concepts, non-sensitive read-only lookup.

Minimum cadence:

• C0/C1 allowed.
• C2 if using handles or inherited context.
• C4 optional unless persisted.

Minimum attestation:

• canonical encoding check;
• schema hash where applicable.

R1 — Internal / operational

Examples: internal graph query, repo metadata, non-sensitive route scan.

Minimum cadence:

• C1 stream inheritance;
• C2 capability/context beacon;
• C4 receipt if persisted.

Minimum attestation:

• schema + source + policy epoch.

R2 — Memory-bearing / knowledge candidate

Examples: CSKG candidate edge, ontology alignment candidate, implicit relation candidate, module boundary candidate.

Minimum cadence:

• C2 context/schema/vocabulary beacon;
• C4 BoundaryReceipt before admission;
• C5 if promoted to semantic memory.

Minimum attestation:

• evidence context;
• matcher/extractor/version receipt;
• claim mode;
• promotion rule if memory write occurs.

R3 — Identity / quasi-identifier / linkage risk

Examples: SameAs, person/account/org/contact/location linkage, source-specific identity merge, behavioral basis vectors.

Minimum cadence:

• C2 Identity-Prime policy and privacy defaults;
• C3 explicit linkage intent;
• C4 quarantine or admission receipt;
• C5 audit report for durable promotion.

Minimum attestation:

• DoNotLearn and DoNotLink default;
• capability;
• provenance;
• identity proof/review artifact;
• non-linkability decision.

R4 — Actuation / security / proof-facing consequence

Examples: worldlet actuation, runtime admission, proof diagnostic publication, finite spectrum report, policy decision, build admission.

Minimum cadence:

• C2 capability/policy/watcher bundle;
• C3 action or publication lease;
• C4 commit/denial receipt;
• C5 release/audit if durable.

Minimum attestation:

• watcher composition receipt;
• source/provenance check;
• action bounds;
• self-perception or equivalent external evidence for physical actions;
• proof/regression receipt for theorem-adjacent outputs.

R5 — Secret / critical / irreversible

Examples: credentials, raw PII/PHI, critical system maps, incident-response details, irreversible actuation, training contamination.

Minimum cadence:

• C2 high-assurance policy and capability;
• C3 explicit break-glass or approved workflow intent;
• C4 mandatory denial/quarantine/admission receipt;
• C5 independent audit and retention/tombstone record.

Minimum attestation:

• no silent processing;
• no fallback to permissive route;
• vault reference instead of raw payload;
• dual control or explicit governance path when applicable;
• DoNotLearn/DoNotLink unless specifically overridden by policy.

Attestation objects

Add or align these records:

CadenceBinding {
  cadence_class,
  frame_kind,
  stream_scope,
  beacon_epoch,
  inherited_context_refs[],
  refresh_rule,
  expiry_rule
}

RiskAssessment {
  risk_tier,
  risk_labels[],
  identity_risk,
  memory_risk,
  action_risk,
  proof_risk,
  privacy_risk,
  consequence_summary
}

AttestationRequirement {
  required_watchers[],
  required_receipts[],
  required_policy_refs[],
  required_evidence_refs[],
  fallback_policy,
  degraded_mode_policy
}

AttestationReceipt {
  input_hash,
  output_hash,
  cadence_binding_hash,
  risk_assessment_hash,
  watcher_decision_hashes[],
  policy_hashes[],
  evidence_hashes[],
  final_decision,
  retention_action
}

Pattern cadence by artifact family

CSKG edge ingest

• Public edge: C1 stream + C2 schema/vocabulary + C4 edge receipt.
• Implicit relation edge: C2 extractor/matcher context + C4 evidence receipt + no semantic promotion without C5.
• SameAs/human linkage: C2 Identity-Prime + C3 linkage intent + C4 quarantine/admit receipt + C5 audit before semantic release.

FSMS memory

• Working memory: C1/C2 with TTL.
• Episode bundle: C4 per episode/trace.
• Semantic memory release: C5 only after promotion rule receipt.
• Forgetting/tombstone: C4 event + C5 release/audit when durable.

Minimal Universe / worldlet

• Sensor trace: C0/C1 sampled frame; C4 before admitted observation.
• Action attempt: C3 intent/lease; C4 commit only after echo/self-perception.
• Dynamics document: C2/C5 DynamicsManifest depending on reuse scope.
• Learned policy update: R4/R5 depending on data; requires C5 attestation.

Proof programme

• Diagnostic computation: C2 context + C4 computation receipt.
• Theorem-adjacent claim: C3 publication intent + C4 proof/regression receipt.
• Release: C5 with non-claim box and validation commands.
• Missing regression/provenance: error/quarantine, never promotion.

Implementation requirement

Add cadence/risk/attestation validation before implementing arbitrary watcher middleware.

Proposed modules:

boundary.py
  BoundaryWatcherDecision
  BoundaryReceipt
  FailClosedCompositionPolicy

cadence.py
  CadenceBinding
  CadenceClass
  RefreshRule
  ExpiryRule

risk.py
  RiskTier
  RiskAssessment
  AttestationRequirement

attestation.py
  AttestationReceipt
  validate_attestation_requirements()

Negative tests

• R3 identity edge sent only as C0 hot frame -> reject.
• R4 action without Beacon-B lease -> reject.
• R4 action with no Beacon-C echo receipt -> attempted_not_admitted.
• R2 candidate edge promoted to semantic memory without C5 release receipt -> reject.
• R5 raw credential in payload instead of vault reference -> quarantine.
• R2 implicit relation missing evidence context -> quarantine.
• R4 finite spectrum report missing regression receipt -> reject.
• fallback flag permits action route without explicit route policy -> reject.

Acceptance criteria addition for #69

• Add cadence/risk/attestation matrix to cskg.vnext or Annex X.
• Define CadenceBinding, RiskAssessment, AttestationRequirement, and AttestationReceipt.
• Add tests proving risk tier controls cadence and attestation requirements.
• Add examples for CSKG, FSMS, Minimal Universe, and proof programme.
• Ensure fallback/degraded mode cannot reduce attestation requirements.