Reference objects are reusable, consumer-independent representations of the
information types defined by Institutional Capability Lineage Architecture. They differ
from reference-traces/, which serialize
complete executions and their governed transitions.
Organizational-memory roles are represented as overlapping annotations within CKC bindings, assemblies, and evidence rather than as additional principal object types. This preserves the compact object contract model while making semantic, procedural, and episodic knowledge functions inspectable.
The evidence bundle also preserves the other direction of the memory loop: CEEs consume authorized assemblies but may produce situated observations, artifacts, practices, and decisions. Such outputs remain candidate knowledge until an identified evidence path and governance decision admit them.
An Assembly is also the persistent record of a bounded operational mandate. It delegates execution-scoped authority without granting canonical change. The CEE may realize it as a policy-dependent local representation or governed access handles. Its MAT record retains assembly and CEE references, substrate and transformation versions, hash/access metadata, evaluation/evidence bindings, and explicit preservation of semantics and authority. It does not assign institutional ownership of the payload. Internal CEE working state remains local unless the evidence contract explicitly selects it.
The initial object catalog is defined through the schemas:
| Object | Structural contract |
|---|---|
| Institutional capability | capability.schema.yaml |
| Capability proposal | capability-proposal.schema.yaml |
| Capability Knowledge Contract | ckc.schema.yaml |
| Registry snapshot | capability-registry.schema.yaml |
| Operational intent | intent.schema.yaml |
| Capability resolution | resolution.schema.yaml |
| Contextual assembly | assembly.schema.yaml |
| CEE-side materialization | materialization.schema.yaml |
| Evidence bundle | evidence-bundle.schema.yaml |
| Governance decision and activation | governance-decision.schema.yaml |
Generic reference instances will be added here only when they can remain independent of a particular execution trace. This avoids presenting partial templates as canonical objects.