{"beats":[{"chapter":"Layer 1","hud":"Intent under drift","id":"pressure","inspect":{"body":"That gap is where unreliable AI work begins: a strong user intent trying to act through weak knowledge boundaries.","label":"Inspect","summary":"The request is clear. The knowledge surface underneath it is not.","title":"Intent arrives before the knowledge stack is ready."},"message":"You want an assistant or agent to do something real with your knowledge.","noun":"fragment","proof":{"bullets":["Distribution already moves knowledge faster than review catches up.","The task arrives before teams have one inspectable knowledge unit.","That makes even reasonable AI use hard to trust."],"claim":"The first problem is not generation. It is unmanaged knowledge entering action.","receipts":["openako-spec-distribution-v1","openako-spec-unified-review-loop-v1"]},"scene_id":"pressure","stage_start":true,"stage_title":"Intent Meets Drift","support":"The job starts with intent, not architecture.","title":"Intent","verb":"fracture"},{"chapter":"Layer 1","hud":"Fragment drift","id":"pressure-2","inspect":{"body":"Fragments can be valuable and still be unsafe to trust together, because nothing yet binds them into one reviewable object.","label":"Inspect","summary":"The task touches many sources before any shared boundary exists.","title":"Drift means the useful pieces never arrive as one thing."},"message":"The first barrier is drift: the knowledge sits in prompts, docs, exports, and connectors.","noun":"fragment","proof":{"bullets":["Prompts, exports, and connectors all feed the same assistants.","Those inputs rarely share one portable review edge.","The system gets content before it gets governance."],"claim":"Knowledge drift is operational, not theoretical.","receipts":["openako-spec-distribution-v1","openako-spec-mcp-interface-contract-v1"]},"scene_id":"pressure","stage_start":false,"stage_title":"Intent Meets Drift","support":"The model sees pieces, not one inspectable unit.","title":"Drift","verb":"fracture"},{"chapter":"Layer 1","hud":"Hidden provenance","id":"pressure-3","inspect":{"body":"That makes inspection and disagreement harder, because the real knowledge surface stays hidden behind the generated response.","label":"Inspect","summary":"People see the answer first and the knowledge structure never appears.","title":"Output is visible sooner than provenance."},"message":"Even a good answer is hard to trust when the source knowledge stays invisible.","noun":"fragment","proof":{"bullets":["Answers arrive faster than their knowledge context.","People cannot cite or compare what they cannot point at.","The missing object boundary becomes a trust bottleneck."],"claim":"Without a visible source unit, trust gets reconstructed from prose.","receipts":["openako-spec-core-v1","openako-spec-unified-review-loop-v1"]},"scene_id":"pressure","stage_start":false,"stage_title":"Intent Meets Drift","support":"People receive output, not the boundary that produced it.","title":"Hidden Sources","verb":"fracture"},{"chapter":"Layer 1","hud":"Boundary loss","id":"pressure-4","inspect":{"body":"The more often the knowledge moves, the more likely teams are to reconstruct its status from memory and surrounding prose.","label":"Inspect","summary":"Meaning, trust, and review no longer arrive as one package.","title":"Knowledge breaks apart when its constraints do not travel with it."},"message":"Once knowledge moves, identity, modality, and review state separate from each other.","noun":"fragment","proof":{"bullets":["Identity drifts when the object is not explicit.","Modality blurs when scenario and actual material mix.","Review state stops travelling with the content."],"claim":"Movement without a shared boundary creates the next failure layer.","receipts":["openako-registry-modality-v1","openako-spec-distribution-v1"]},"scene_id":"pressure","stage_start":false,"stage_title":"Intent Meets Drift","support":"That is where the next-order errors start.","title":"Boundary Loss","verb":"fracture"},{"chapter":"Layer 1","hud":"Need one unit","id":"pressure-5","inspect":{"body":"That unit is the bridge from scattered fragments to trustworthy operations.","label":"Inspect","summary":"The system needs one object before it needs a bigger world.","title":"The next answer has to be a unit, not another layer of explanation."},"message":"So the first real requirement is simple: one unit you can inspect, cite, and move.","noun":"fragment","proof":{"bullets":["Inspection needs one shared reference.","Transport needs one stable identity.","Governance needs one explicit boundary."],"claim":"The first credible fix is a reusable governed unit.","receipts":["openako-spec-core-v1","openako-constraint-ako-envelope-v1"]},"scene_id":"pressure","stage_start":false,"stage_title":"Intent Meets Drift","support":"Without that, every later fix is temporary.","title":"Requirement","verb":"fracture"},{"chapter":"Layer 2","hud":"One bounded unit","id":"ako","inspect":{"body":"Once knowledge becomes one object, people and tools can point at the same thing instead of inferring structure from output.","label":"Inspect","summary":"This is the first answer to drift.","title":"The core is the claim. The boundary makes it one object."},"message":"That unit starts as one bounded knowledge object.","noun":"core","proof":{"bullets":["The object boundary is explicit in the core model.","That boundary is what makes inspection and transport possible.","Scale comes later, after the unit works."],"claim":"The model starts with a governed unit, not a giant knowledge base.","receipts":["openako-spec-core-v1","openako-constraint-ako-envelope-v1"]},"scene_id":"ako","stage_start":true,"stage_title":"One Unit","support":"OpenAKO later names it an AKO. The important part first is the boundary.","title":"One Unit","verb":"bound"},{"chapter":"Layer 2","hud":"Inspectable size","id":"ako-2","inspect":{"body":"The bounded object stays small on purpose so teams can inspect the object itself instead of only its summary.","label":"Inspect","summary":"Inspection fails when the first object is already too large to reason about.","title":"A useful unit has to remain legible."},"message":"The object should stay small enough to inspect directly.","noun":"core","proof":{"bullets":["Governance starts with an inspectable object.","The boundary exists before large-scale composition.","The object is the thing that moves, not just its prose."],"claim":"The reusable unit is intentionally compact.","receipts":["openako-spec-core-v1","openako-conformance-fixture-ako-brand-identity-v1"]},"scene_id":"ako","stage_start":false,"stage_title":"One Unit","support":"A governed unit fails if it begins as a giant hidden bundle.","title":"Small Enough To Inspect","verb":"bound"},{"chapter":"Layer 2","hud":"Shared reference","id":"ako-3","inspect":{"body":"That shared object is what makes review and automation line up instead of drifting apart.","label":"Inspect","summary":"Different actors can disagree, but they still refer to the same unit.","title":"The object is what survives across roles."},"message":"People, tools, and agents should all point at the same object.","noun":"core","proof":{"bullets":["People can inspect it.","Tools can cite it.","Agents can use it without inventing their own hidden version."],"claim":"A governed object gives everyone the same reference point.","receipts":["openako-spec-core-v1","openako-spec-mcp-interface-contract-v1"]},"scene_id":"ako","stage_start":false,"stage_title":"One Unit","support":"The object becomes the shared reference, not the generated answer.","title":"Shared Reference","verb":"bound"},{"chapter":"Layer 2","hud":"Portable object","id":"ako-4","inspect":{"body":"That is what makes downstream routing and agent use possible without losing the original unit.","label":"Inspect","summary":"A portable object carries itself, not just a copy of its content.","title":"Portability begins with object identity."},"message":"The unit has to travel without changing what it is.","noun":"core","proof":{"bullets":["Identity stays with the object.","Boundary stays with the object.","Later delivery formats still refer back to the same source."],"claim":"The object is designed to be portable, not trapped in one repository context.","receipts":["openako-conformance-fixture-ako-brand-identity-v1","openako-spec-distribution-v1"]},"scene_id":"ako","stage_start":false,"stage_title":"One Unit","support":"Portability starts at the object boundary, not at export time.","title":"Portable","verb":"bound"},{"chapter":"Layer 2","hud":"Active Knowledge Object","id":"ako-5","inspect":{"body":"By the time the name appears, the job of the object should already make intuitive sense.","label":"Inspect","summary":"The term follows the need, not the other way around.","title":"AKO is the name for the governed unit that solves drift at the object level."},"message":"That is the moment OpenAKO enters: one reusable Active Knowledge Object.","noun":"core","proof":{"bullets":["The core model defines the unit boundary.","Conformance fixtures treat the object as portable and inspectable.","That is why the name matters operationally."],"claim":"AKO is defined as the reusable governed unit, not as a vague content blob.","receipts":["openako-spec-core-v1","openako-conformance-fixture-ako-brand-identity-v1"]},"scene_id":"ako","stage_start":false,"stage_title":"One Unit","support":"Now the term names a need the visitor has already felt.","title":"AKO","verb":"bound"},{"chapter":"Layer 3","hud":"Boundary with rules","id":"governance","inspect":{"body":"That is where governance becomes operational rather than decorative.","label":"Inspect","summary":"It also carries how the object should be understood and used.","title":"The boundary has to carry more than shape."},"message":"A bounded object still fails if its rules live somewhere else.","noun":"boundary","proof":{"bullets":["Trust depends on what travels with the object.","Meaning and review state cannot stay behind.","That is why governance binds at the boundary."],"claim":"A unit is not enough if its rules remain external.","receipts":["openako-spec-profile-mechanism-v1","openako-spec-validation-v1"]},"scene_id":"governance","stage_start":true,"stage_title":"Rules Travel With It","support":"Trust collapses when meaning and constraints must be reconstructed.","title":"Rules With The Object","verb":"govern"},{"chapter":"Layer 3","hud":"Profiled boundary","id":"governance-2","inspect":{"body":"That makes later validation and transport much more reliable.","label":"Inspect","summary":"Shape matters because it limits interpretation before the handoff.","title":"A profile turns a vague object into a use-ready one."},"message":"Profiles shape what the object is allowed to be for a given use.","noun":"boundary","proof":{"bullets":["Profiles determine how the object is formed.","The object does not need new ad hoc rules in each tool.","Reuse gets safer when the profile stays explicit."],"claim":"Profiles are part of the object model because shape affects trust.","receipts":["openako-spec-profile-mechanism-v1"]},"scene_id":"governance","stage_start":false,"stage_title":"Rules Travel With It","support":"The object does not improvise its own meaning.","title":"Profiles","verb":"govern"},{"chapter":"Layer 3","hud":"Validated boundary","id":"governance-3","inspect":{"body":"That shared pass/fail surface is what keeps humans and automation aligned.","label":"Inspect","summary":"A trustworthy boundary can be checked, not just described.","title":"Validation makes the object operationally testable."},"message":"Validation gives the boundary a repeatable pass or fail surface.","noun":"boundary","proof":{"bullets":["The same object can be checked across teams and tools.","Validation narrows ambiguity before use.","The boundary becomes a real operational surface."],"claim":"Validation makes governance repeatable instead of implicit.","receipts":["openako-spec-validation-v1"]},"scene_id":"governance","stage_start":false,"stage_title":"Rules Travel With It","support":"People and systems can check the same object the same way.","title":"Validation","verb":"govern"},{"chapter":"Layer 3","hud":"Modal clarity","id":"governance-4","inspect":{"body":"That distinction becomes essential once objects begin to compose into larger worlds.","label":"Inspect","summary":"Actual and scenario material must stay visible as different kinds of knowledge.","title":"Mode matters because not all knowledge is making the same claim."},"message":"Modality keeps actual, scenario, and fictional knowledge distinct.","noun":"boundary","proof":{"bullets":["Actual and scenario material can coexist without collapsing together.","The object declares its mode instead of hiding it.","That keeps later composition and review honest."],"claim":"Modality is explicit because useful worlds still need truthful separation.","receipts":["openako-registry-modality-v1"]},"scene_id":"governance","stage_start":false,"stage_title":"Rules Travel With It","support":"Without modality, a useful object can still mislead.","title":"Modality","verb":"govern"},{"chapter":"Layer 3","hud":"Trustworthy handoff","id":"governance-5","inspect":{"body":"That is what makes later composition and derivation possible without starting over.","label":"Inspect","summary":"The object now carries enough structure to survive movement.","title":"A governed boundary turns the object into a safe handoff surface."},"message":"Now the object can move with identity, rules, and review state intact.","noun":"boundary","proof":{"bullets":["Identity stays intact.","Constraints stay intact.","Review state stays attached to the same object."],"claim":"Trust appears when the object and its rules travel together.","receipts":["openako-spec-profile-mechanism-v1","openako-spec-validation-v1","openako-registry-modality-v1"]},"scene_id":"governance","stage_start":false,"stage_title":"Rules Travel With It","support":"That is the first trustworthy handoff.","title":"First Trustworthy Handoff","verb":"govern"},{"chapter":"Layer 4","hud":"Need composition","id":"worlding","inspect":{"body":"That is the problem worlding solves.","label":"Inspect","summary":"The next question is how bounded units gather without collapsing into sludge.","title":"Real work needs relations between units, not just one good object."},"message":"Most real tasks need several governed objects at once.","noun":"matrix","proof":{"bullets":["Several governed objects often belong in one working frame.","Composition must stay inspectable.","That requires an explicit world candidate."],"claim":"Operational AI work usually needs a composed scope, not a lone object.","receipts":["openako-spec-catalog-resolution-v1","openako-spec-world-resolution-v1"]},"scene_id":"worlding","stage_start":true,"stage_title":"One Unit Is Not Enough","support":"One good object is not yet a working knowledge world.","title":"Need More Than One","verb":"compose"},{"chapter":"Layer 4","hud":"World selection","id":"worlding-2","inspect":{"body":"That preserves intentionality instead of letting a bigger blob appear by accident.","label":"Inspect","summary":"A world starts by deciding what enters the frame.","title":"Selection is the first act of composition."},"message":"The next problem is choosing which objects belong together.","noun":"matrix","proof":{"bullets":["Catalog resolution determines what can gather.","Selection makes scope explicit.","The world begins as a candidate, not a claim."],"claim":"Worlding begins with controlled selection.","receipts":["openako-spec-catalog-resolution-v1"]},"scene_id":"worlding","stage_start":false,"stage_title":"One Unit Is Not Enough","support":"Composition starts with explicit selection, not accumulation.","title":"Selection","verb":"compose"},{"chapter":"Layer 4","hud":"Candidate world","id":"worlding-3","inspect":{"body":"The candidate state is what lets review and comparison happen before the world is treated as settled.","label":"Inspect","summary":"It is larger than one object, but still not an opaque store.","title":"A world is a structured candidate arrangement."},"message":"Those objects gather into a candidate world.","noun":"matrix","proof":{"bullets":["The world is assembled from governed objects.","The candidate can still be questioned.","That keeps large-scale knowledge work reviewable."],"claim":"The world is modeled as an explicit candidate surface.","receipts":["openako-spec-world-resolution-v1","openako-conformance-fixture-world-frame-v1"]},"scene_id":"worlding","stage_start":false,"stage_title":"One Unit Is Not Enough","support":"The parts stay inspectable even while they form a larger frame.","title":"Candidate World","verb":"compose"},{"chapter":"Layer 4","hud":"Candidate comparison","id":"worlding-4","inspect":{"body":"That matters because composition without comparison becomes another hidden merge.","label":"Inspect","summary":"The candidate stage preserves disagreement as a useful operation.","title":"Comparison is only possible because the world is not yet sealed."},"message":"Because the world is still a candidate, it can be reviewed and compared.","noun":"matrix","proof":{"bullets":["Comparison is part of composition.","Conflicts can still be surfaced here.","That makes sealing meaningful later."],"claim":"World candidates remain open to review before they become resolved state.","receipts":["openako-spec-world-resolution-v1","openako-spec-review-packets-v1"]},"scene_id":"worlding","stage_start":false,"stage_title":"One Unit Is Not Enough","support":"Teams can still ask what changed, what is missing, and what conflicts.","title":"Comparison","verb":"compose"},{"chapter":"Layer 4","hud":"Working scope","id":"worlding-5","inspect":{"body":"The system can now work across many governed units while keeping each one explicit.","label":"Inspect","summary":"That is the key shift from object to world.","title":"Composition creates operational scope without erasing the parts."},"message":"Worlding turns many bounded units into one working scope without collapsing them.","noun":"matrix","proof":{"bullets":["Many units can now act together.","Their boundaries still remain visible.","The world is now ready for resolution."],"claim":"Worlding solves scope before sealing solves reproducibility.","receipts":["openako-spec-catalog-resolution-v1","openako-spec-world-resolution-v1"]},"scene_id":"worlding","stage_start":false,"stage_title":"One Unit Is Not Enough","support":"That is what makes larger AI work manageable.","title":"Working Scope","verb":"compose"},{"chapter":"Layer 5","hud":"Need resolution","id":"seal","inspect":{"body":"That is why the next operation is resolution into one proof-bearing object.","label":"Inspect","summary":"Use needs one cited state, not many private interpretations.","title":"A candidate world cannot yet serve as the stable source."},"message":"A candidate world is useful, but it is not yet reproducible.","noun":"seal","proof":{"bullets":["Candidates remain open by design.","Downstream work needs one stable reference.","That is what sealing provides."],"claim":"Use without a resolved state quickly becomes version drift.","receipts":["openako-spec-world-resolution-v1"]},"scene_id":"seal","stage_start":true,"stage_title":"Candidate Is Still Not Enough","support":"If every downstream step invents its own snapshot, trust breaks again.","title":"Candidate Is Not Reproducible","verb":"seal"},{"chapter":"Layer 5","hud":"Resolved state","id":"seal-2","inspect":{"body":"That does not erase review. It gives review one thing to review.","label":"Inspect","summary":"The world stops being only a possibility and becomes a reference.","title":"Resolution turns a working candidate into one cited state."},"message":"So the world has to resolve into one cited state.","noun":"seal","proof":{"bullets":["The candidate phase stays useful.","The resolved phase becomes citeable.","Downstream use now has one shared source."],"claim":"Resolution separates candidate assembly from settled state.","receipts":["openako-spec-world-resolution-v1","openako-spec-review-packets-v1"]},"scene_id":"seal","stage_start":false,"stage_title":"Candidate Is Still Not Enough","support":"This is the point where teams stop pointing at private versions.","title":"Resolve","verb":"seal"},{"chapter":"Layer 5","hud":"Proof object","id":"seal-3","inspect":{"body":"The proof object becomes the stable source for derivation, comparison, and action.","label":"Inspect","summary":"That is what downstream systems can point back to.","title":"The seal is not just a brighter scene. It marks one settled world."},"message":"The resolved world becomes a proof object.","noun":"seal","proof":{"bullets":["Proof matters where use becomes actionable.","The seal anchors later receipts and interfaces.","That keeps downstream work aligned."],"claim":"The resolved world is what later surfaces trust.","receipts":["openako-spec-world-resolution-v1","openako-spec-unified-review-loop-v1"]},"scene_id":"seal","stage_start":false,"stage_title":"Candidate Is Still Not Enough","support":"Now packs, reviews, and interfaces can all refer back to the same state.","title":"Proof Object","verb":"seal"},{"chapter":"Layer 5","hud":"Resolved comparison","id":"seal-4","inspect":{"body":"That is what makes large-scale governance practical instead of rhetorical.","label":"Inspect","summary":"The question becomes what changed between states, not what somebody remembers.","title":"Resolved states make comparison precise."},"message":"Once sealed, two world states can be compared without guesswork.","noun":"seal","proof":{"bullets":["Review can operate on concrete differences.","Multiple versions no longer imply private snapshots.","Teams can discuss state transitions directly."],"claim":"Sealed states are comparable because they are explicit and repeatable.","receipts":["openako-spec-review-packets-v1","openako-spec-world-resolution-v1"]},"scene_id":"seal","stage_start":false,"stage_title":"Candidate Is Still Not Enough","support":"Review becomes about differences between resolved states, not vibes.","title":"Compare Versions","verb":"seal"},{"chapter":"Layer 5","hud":"Stable source world","id":"seal-5","inspect":{"body":"That is why the later lifecycle can stay smaller and cleaner.","label":"Inspect","summary":"Derivation, transport, and use stop inventing their own knowledge base.","title":"The sealed world becomes the authoritative source for what comes next."},"message":"From here on, downstream work derives from one stable source.","noun":"seal","proof":{"bullets":["The source world is now reproducible.","Downstream packs refer back to it.","The next problem becomes selective delivery."],"claim":"Sealing matters because it stabilizes everything downstream.","receipts":["openako-spec-world-resolution-v1","openako-spec-bundling-v1"]},"scene_id":"seal","stage_start":false,"stage_title":"Candidate Is Still Not Enough","support":"That is what makes the next steps precise.","title":"Stable Source","verb":"seal"},{"chapter":"Layer 6","hud":"Need less","id":"slice","inspect":{"body":"That keeps the task scoped while preserving a trustworthy link back to the larger source.","label":"Inspect","summary":"The next answer is selective derivation.","title":"A resolved world is stable, but it is still too much for most tasks."},"message":"Most tasks should not receive the whole resolved world.","noun":"slice","proof":{"bullets":["Whole-world delivery overwhelms many tasks.","Specific roles need different subsets.","Derivation narrows the working surface."],"claim":"Good delivery sends less, not more.","receipts":["openako-spec-bundling-v1"]},"scene_id":"slice","stage_start":true,"stage_title":"Most Tasks Need Less","support":"Too much context creates noise, risk, and unnecessary review burden.","title":"Whole World Is Too Much","verb":"derive"},{"chapter":"Layer 6","hud":"Just enough context","id":"slice-2","inspect":{"body":"That is what makes delivery precise instead of expansive.","label":"Inspect","summary":"It reduces volume while keeping provenance intact.","title":"The slice exists to fit the job, not to mirror the whole world."},"message":"The task needs a derived slice of the larger source.","noun":"slice","proof":{"bullets":["The slice is smaller than the world on purpose.","The derivation step stays explicit.","Use becomes easier to review."],"claim":"Derivation exists to send the right subset.","receipts":["openako-spec-bundling-v1","openako-portable-pack-openako-main-v1beta-20260325-v1.ako.json"]},"scene_id":"slice","stage_start":false,"stage_title":"Most Tasks Need Less","support":"Less context is often the more trustworthy delivery.","title":"Just Enough","verb":"derive"},{"chapter":"Layer 6","hud":"Role-fit delivery","id":"slice-3","inspect":{"body":"That keeps knowledge useful without forcing every task to absorb the full world.","label":"Inspect","summary":"Different work surfaces receive different shapes of the same governed source.","title":"Derivation makes delivery role-fit instead of one-size-fits-all."},"message":"Different roles need different slices.","noun":"slice","proof":{"bullets":["The source world stays stable.","The slices vary by need.","Review remains tied back to the same world."],"claim":"Role-fit delivery comes from derivation, not from rewriting the source each time.","receipts":["openako-spec-bundling-v1","openako-catalog-manifest-openako-main-v1beta-20260325-v1.ako.json"]},"scene_id":"slice","stage_start":false,"stage_title":"Most Tasks Need Less","support":"Support, policy, and agent tasks rarely need the same pack.","title":"Role Fit","verb":"derive"},{"chapter":"Layer 6","hud":"Derived with provenance","id":"slice-4","inspect":{"body":"The slice is useful precisely because it remains accountable to the world that produced it.","label":"Inspect","summary":"That is what stops derivation from becoming information loss.","title":"A smaller delivery should still point back to the larger source."},"message":"The slice stays connected to the world it came from.","noun":"slice","proof":{"bullets":["The slice is linked to the resolved source.","Proof and review can still climb back to the world.","That keeps delivery honest."],"claim":"Derivation narrows scope without severing provenance.","receipts":["openako-spec-bundling-v1","openako-portable-pack-openako-main-v1beta-20260325-v1.ako.json"]},"scene_id":"slice","stage_start":false,"stage_title":"Most Tasks Need Less","support":"Derivation should reduce volume, not erase provenance.","title":"Keep The Link","verb":"derive"},{"chapter":"Layer 6","hud":"Task-ready slice","id":"slice-5","inspect":{"body":"That makes the next problem obvious: how to move it without losing its edge.","label":"Inspect","summary":"It is still governed, just more specific.","title":"The slice is the first delivery surface that fits the job."},"message":"Now knowledge is shaped for a task instead of dumped wholesale.","noun":"slice","proof":{"bullets":["The world remains stable.","The slice becomes the working delivery.","Transport can now happen on a smaller surface."],"claim":"Task-fit delivery is the bridge from world state to operational use.","receipts":["openako-spec-bundling-v1","openako-spec-distribution-v1"]},"scene_id":"slice","stage_start":false,"stage_title":"Most Tasks Need Less","support":"That is the start of real operational delivery.","title":"Task Surface","verb":"derive"},{"chapter":"Layer 7","hud":"Need an explicit route","id":"channel","inspect":{"body":"That is what makes knowledge transport a first-class surface instead of invisible glue.","label":"Inspect","summary":"The route itself must preserve what moved and why.","title":"Movement is part of governance, not something that happens after it."},"message":"Transport creates a new problem: knowledge can lose its edge in motion.","noun":"channel","proof":{"bullets":["The slice leaves its source world.","Its route must remain explicit.","Otherwise the handoff becomes another mystery blob."],"claim":"Transport is modeled because governed knowledge has to travel without dissolving.","receipts":["openako-spec-distribution-v1"]},"scene_id":"channel","stage_start":true,"stage_title":"Movement Breaks Trust","support":"A good slice still fails if the handoff path is opaque.","title":"Movement Problem","verb":"route"},{"chapter":"Layer 7","hud":"Explicit route","id":"channel-2","inspect":{"body":"The route becomes a trustworthy handoff surface rather than a hidden copy step.","label":"Inspect","summary":"That keeps transport visible instead of implied.","title":"A good route names the object, its source, and its destination."},"message":"The route needs to say what moved, from where, and toward what.","noun":"channel","proof":{"bullets":["You can see what moved.","You can see where it came from.","You can see what surface will receive it."],"claim":"Explicit routing keeps the object boundary visible during motion.","receipts":["openako-spec-distribution-v1","openako-ecosystem-stash-index-v1.ako.json"]},"scene_id":"channel","stage_start":false,"stage_title":"Movement Breaks Trust","support":"Movement becomes part of governance.","title":"Explicit Route","verb":"route"},{"chapter":"Layer 7","hud":"Portable handoff","id":"channel-3","inspect":{"body":"That preserves identity and derivation even while the knowledge is in motion.","label":"Inspect","summary":"The pack is the traveling surface, not the loss of the object.","title":"Portability matters because the slice cannot stay trapped in one system."},"message":"Portable packs keep the object boundary visible while knowledge travels.","noun":"channel","proof":{"bullets":["The pack is built for movement.","Its provenance is still visible.","The receiving side gets a governed surface."],"claim":"Portable packs preserve object identity during movement.","receipts":["openako-portable-pack-openako-main-v1beta-20260325-v1.ako.json","openako-spec-distribution-v1"]},"scene_id":"channel","stage_start":false,"stage_title":"Movement Breaks Trust","support":"The handoff remains a governed move, not an ad hoc paste.","title":"Portable Pack","verb":"route"},{"chapter":"Layer 7","hud":"Visible routing","id":"channel-4","inspect":{"body":"That helps people and systems understand how governed knowledge is actually distributed.","label":"Inspect","summary":"Knowledge movement stops pretending to be invisible infrastructure.","title":"The route becomes clearer when addresses and stores are explicit."},"message":"Registries and stashes make routing explicit instead of hidden.","noun":"channel","proof":{"bullets":["The destination is visible.","The addressing surface is visible.","The route stays inspectable during transport."],"claim":"Routing surfaces stay explicit through registries and stashes.","receipts":["openako-ecosystem-registry-v1.ako.json","openako-ecosystem-stash-index-v1.ako.json"]},"scene_id":"channel","stage_start":false,"stage_title":"Movement Breaks Trust","support":"You can see where governed knowledge lives and how it was addressed.","title":"Registries","verb":"route"},{"chapter":"Layer 7","hud":"Ready handoff","id":"channel-5","inspect":{"body":"That leads directly to the final problem: the interface for action.","label":"Inspect","summary":"Transport has preserved enough structure for real use.","title":"The pack arrives as a governed handoff surface."},"message":"Now the slice can arrive somewhere else without becoming a mystery blob.","noun":"channel","proof":{"bullets":["The object identity survives.","The derivation remains visible.","The receiving side is ready for explicit use."],"claim":"Transport is successful when the receiving side gets a stable governed surface.","receipts":["openako-spec-distribution-v1","openako-portable-pack-openako-main-v1beta-20260325-v1.ako.json"]},"scene_id":"channel","stage_start":false,"stage_title":"Movement Breaks Trust","support":"The next question is how that destination uses it.","title":"Ready Handoff","verb":"route"},{"chapter":"Layer 8","hud":"Stable use surface","id":"port","inspect":{"body":"The port is the governed use surface for the final handoff into action.","label":"Inspect","summary":"That interface is what keeps action explicit.","title":"Arrival is not enough. The receiving side still needs a clean interface."},"message":"Assistants and agents need one stable use surface.","noun":"port","proof":{"bullets":["A traveling pack still needs a use surface.","That surface must retrieve and cite explicitly.","Otherwise the knowledge disappears into hidden prompts again."],"claim":"The last problem is action through a stable interface.","receipts":["openako-spec-mcp-interface-contract-v1","openako-spec-agent-skills-v1"]},"scene_id":"port","stage_start":true,"stage_title":"Use Needs A Stable Surface","support":"The task is not finished when the pack arrives.","title":"Use Surface","verb":"enact"},{"chapter":"Layer 8","hud":"Explicit interface","id":"port-2","inspect":{"body":"That keeps knowledge use and knowledge source connected in action.","label":"Inspect","summary":"The interface stays explicit instead of becoming prompt paste.","title":"The port is where governed knowledge meets actual work."},"message":"A port gives the tool or assistant a clear way to retrieve and cite.","noun":"port","proof":{"bullets":["Retrieval becomes explicit.","Citation becomes explicit.","Action no longer hides the source."],"claim":"Stable interfaces are what keep governed knowledge usable in practice.","receipts":["openako-spec-mcp-interface-contract-v1"]},"scene_id":"port","stage_start":false,"stage_title":"Use Needs A Stable Surface","support":"Action becomes explicit instead of disappearing into hidden prompts.","title":"Interface","verb":"enact"},{"chapter":"Layer 8","hud":"Knowledge into action","id":"port-3","inspect":{"body":"The interface remains stable while the action becomes role-fit.","label":"Inspect","summary":"That is how agents act with knowledge rather than merely on top of it.","title":"Skills join knowledge use and action without collapsing them together."},"message":"Agent skills link governed knowledge to governed action.","noun":"port","proof":{"bullets":["The action surface stays named.","The knowledge surface stays named.","The two remain linked without becoming one blob."],"claim":"Agent skills make the knowledge-action link explicit.","receipts":["openako-spec-agent-skills-v1"]},"scene_id":"port","stage_start":false,"stage_title":"Use Needs A Stable Surface","support":"The system can act without pretending the knowledge and the action are the same thing.","title":"Skills","verb":"enact"},{"chapter":"Layer 8","hud":"Shared governed source","id":"port-4","inspect":{"body":"The object, the world, the slice, the route, and the interface all remain connected.","label":"Inspect","summary":"That is the practical payoff of the whole lifecycle.","title":"Different actors can now use the same governed source through explicit surfaces."},"message":"The same governed object can now serve people, assistants, and agents.","noun":"port","proof":{"bullets":["People can review it.","Assistants can retrieve it.","Agents can act through it."],"claim":"One governed source can support many kinds of action.","receipts":["openako-spec-core-v1","openako-spec-mcp-interface-contract-v1","openako-spec-agent-skills-v1"]},"scene_id":"port","stage_start":false,"stage_title":"Use Needs A Stable Surface","support":"Everyone meets the same source through a role-fit surface.","title":"Human And Agent","verb":"enact"},{"chapter":"Layer 8","hud":"Full governed lifecycle","id":"port-5","inspect":{"body":"That is why the story begins with the user problem and ends with the governed lifecycle.","label":"Inspect","summary":"The product matters because it stabilizes the handoffs between intent and action.","title":"OpenAKO is the answer once the visitor has seen the whole chain of failures."},"message":"This is the full answer: knowledge that can be inspected, governed, derived, moved, and used.","noun":"port","proof":{"bullets":["The object solves drift.","The lifecycle solves the later handoffs.","The use surface keeps action explicit."],"claim":"The value is the full chain: inspectable unit, governed rules, composed world, resolved source, derived pack, explicit route, stable interface.","receipts":["openako-spec-core-v1","openako-spec-world-resolution-v1","openako-spec-bundling-v1","openako-spec-distribution-v1","openako-spec-mcp-interface-contract-v1"]},"scene_id":"port","stage_start":false,"stage_title":"Use Needs A Stable Surface","support":"OpenAKO matters because it solves the next problem before it breaks the next handoff.","title":"OpenAKO Answer","verb":"enact"}],"canonical_url":"https://openako.org/","description":"The first public OpenAKO briefing: a cyberdeck walkthrough of how governed knowledge moves from intent to trustworthy AI use.","id":"https://openako.org/","intro":{"body":"This is the first public explanation of OpenAKO. The repository is not public yet. This walkthrough exists to make the problem, the model, and the promise legible.","label":"Problem-first brief","title":"Each stage solves the next-order problem."},"stages":[{"first_beat_id":"pressure","id":"pressure","label":"Layer 1","title":"Intent Meets Drift"},{"first_beat_id":"ako","id":"ako","label":"Layer 2","title":"One Unit"},{"first_beat_id":"governance","id":"governance","label":"Layer 3","title":"Rules Travel With It"},{"first_beat_id":"worlding","id":"worlding","label":"Layer 4","title":"One Unit Is Not Enough"},{"first_beat_id":"seal","id":"seal","label":"Layer 5","title":"Candidate Is Still Not Enough"},{"first_beat_id":"slice","id":"slice","label":"Layer 6","title":"Most Tasks Need Less"},{"first_beat_id":"channel","id":"channel","label":"Layer 7","title":"Movement Breaks Trust"},{"first_beat_id":"port","id":"port","label":"Layer 8","title":"Use Needs A Stable Surface"}],"summary":"OpenAKO is a model for giving knowledge boundaries, provenance, review state, and portability so humans, assistants, and agents can act on it safely.","title":"OpenAKO","url":"https://openako.org/"}