[Contracts] Release procedural graph, guidance context and evaluation receipt contracts

[seonghobae]

Parent: ContextualWisdomLab/.github#2067. First local implementation: ContextualWisdomLab/noema#585, authored head 5813ee1cb8958aa25e622fe31adfa8dc229f2e3c. This issue requests owner-led contract work; it does not publish a contract or authorize consumers to import that mutable feature branch.

Required deliverables

Publish language-neutral versioned schemas for procedural graph artifacts, advisory execution contexts, evaluation receipts and candidate-screening decisions. Preserve the Noema-local versus released-wire distinction: noema.procedural-graph/v1 and its ordered JSON hashing are local implementation choices, NOT an existing interoperable release.

Graph identity needs tenant/task/graph ID, schema revision, content digest, parent/version lineage, nodes, directed relations and bounded condition/guidance/pitfalls data. Execution context needs exact graph digest, execution/scope identity, localized versus abstained state and advisory_only semantics. Separate graph identity, structure identity, evidence identity, approval and deployment authority.

Define digest/canonicalization rules and equivalent TypeScript/Python/Rust fixtures; reject inconsistent Unicode, number, array ordering or unknown authority-field encodings instead of letting language coercions change identity. Explicitly define relation direction and product-specific terminal/cycle validation profiles. Do not turn advice into executable dependencies.

Evaluation receipts must bind authenticated producer/schema/version, exact candidate/base digests, pre-registered dataset/model/tool/rubric/environment protocol, complete paired held-out case-set identity, evidence timestamps/revocation and score/safety observations. Include strict missing/NaN/infinite/duplicate/mismatched-case rejection fixtures. Authenticated receipt verification and privacy controls are separate from equality of digest strings.

Candidate screening remains non-authoritative: even arithmetic non-regression cannot activate, grant tools, approve a PR or relax policy. Reject-memory identity must include exact base, candidate structure, evaluation protocol and actual case partition/minimum count; don't leak validation examples into refiner prompts or global negative memory.

Acceptance

• Read live open contracts/EAC lanes; extend the canonical owner lane rather than cloning its source.
• Add schemas, positive/hostile conformance fixtures, compatibility policy and immutable artifact/provenance evidence.
• Establish a released version before any cross-repository production consumer is enabled.
• Have Noema and at least one independent consumer prove the same canonical digests and fail-closed conformance.
• Link exact release and consumer evidence to the parent adoption matrix.

No cross-service SQL, copied provider routing, raw credential/PII/hidden-reasoning storage, or sibling PR-head runtime dependency. Existing policy/approval and Keyverse ownership remain unchanged.

[seonghobae]

Ownership follow-through from the user's ConceptWeave request: ConceptWeave#42 and Draft #43 at exact 300fed966643fa4bf2c4be29514b8796da764166 now define a local procedural-model authoring/revision profile. The central plan .github#2067 was updated to assign model authoring/alignment/semantic validation/rejection history/governed publication to ConceptWeave while preserving Noema execution-local projections and guidance.

Please carry both sides into this existing contract-owner lane: (1) ConceptWeave's evidence-bound procedural representation/release, (2) Noema's versioned execution projection. Neither the new local 0.1.0-draft.1 schemas nor Noema's local hashing are a CGC release. Define canonical identity/digest, profile/direction/locale semantics, source/review/evaluation binding and explicit projection incompatibility without copying either runtime.

Acceptance must include Rust/TypeScript cross-language conformance and complete released-projection round trips, including unknown/oversized input, missing entry/endpoint, duplicate logical identity, ambiguous source/tenant/base binding, invalid evidence and forbidden authority expansion. Shape-positive semantic-gap fixtures in ConceptWeave are deliberately not valid executable graphs. Existing #28 provenance, held-out governance and immutable-release requirements remain; this comment supplies a producer counterpart, not release/deployment evidence.

[seonghobae]

Fresh Noema consumer handoff after protected #603/#604 convergence:

• Noema protected source now has a point-in-time publication preflight that reconciles its admitted current State / Checkpoint evaluation-history position with its distinct Policy / Approval CAS position. The receipt remains publicationAuthorized:false and activationAuthorized:false.
• #604 normal-merged the canonical documentation convergence; Noema intentionally has no actual graph-publication transaction yet.
• Fresh owner release inventory remains empty, so Noema will not import a mutable CGC branch/PR/package head.

For the procedural slice, the released CGC authority needs enough immutable wire identity to let an eventual Noema publisher bind one exact admitted preflight to a graph artifact without turning CGC into Noema Policy / Approval or product graph truth. Please preserve the existing #28 acceptance and ensure the released profile makes these distinctions machine-testable:

1. graph artifact/schema/profile identity and canonical digest rules;
2. exact lineage/version identity required to reject a different graph under the same logical graph id;
3. evaluation/advisory receipt profile identity separate from approval/publication/activation state;
4. explicit non-authority semantics for advisory/evaluation fields so eligibleForApproval, a preflight receipt, or matching digest cannot itself authorize publication/activation;
5. equivalent hostile cross-language fixtures covering canonicalization drift, unknown authority fields, Unicode/number/array differences, graph/evidence substitution, and schema/profile version mismatch;
6. immutable release coordinates and provenance that a Noema consumer can pin and independently verify.

Noema consumer acceptance should occur only after an immutable owner release exists and should version-bump that released contract rather than copying owner source. Keyverse current signer-trust selection is being tracked separately at ContextualWisdomLab/keyverse#156; identity/key custody remains outside CGC and Noema graph semantics.

[seonghobae]

Fresh Noema consumer-side handoff after protected #721 integration (2026-09-17 KST):

• Noema is now protected at verified main@f38962869307a45b3b6e65692b2acbabb075e0eb; the procedural Policy / Approval documentation/test convergence is merged and Noema currently has no open PR. Publication and activation remain fail closed.
• CGC still has no GitHub Release, so Noema will not consume a mutable CGC PR/branch/package head.
• The current CGC dependency-root candidate feat: add typed context assertions and lock-checked installs #4 is still Draft at 794e20f31b3e0c1a7958c99cc8535d23b0c25f82 on develop@99cb5468ba3c15c5e79688f53dee74724fae2d13. Its own current authority records that the repository still has default_branch=develop, intended protected integration is main, and the exact head is non-passing because central CodeQL and Dependency Review gates fail.
• Those are owner/control-plane prerequisites rather than Noema defects: .github#1137 owns protect-main-first/default-branch convergence; .github#712 owns the current CodeQL/workflow dispatch-verdict defect; .github#810 owns fail-closed Dependency Review availability/baseline provenance; .github#772 owns the structurally impossible solo-maintainer approval-count rule without weakening deterministic gates.

Please keep #28 release acceptance dependency-root-first: converge the central governance/security prerequisites, rebuild/restack the CGC stack from the resulting protected integration authority, reacquire exact-head package/security/conformance/provenance evidence, and publish one immutable versioned contract. Noema will then version-bump only that released authority and add hostile consumer regressions for stale/changed contract identity. No predecessor/staged CGC head should be promoted to consumer authority merely because Noema is ready.