walkthrough.md

Guided walkthrough

Allow five to eight minutes for the canonical path.

1. Keep Recorded Replay selected. Confirm the disclosure says no provider call is occurring.
2. In User Workspace, read the three software knowledge layers and the Research Brief.
3. Ask the User-side Agent. Inspect the plan and the Runtime's Context, Policy, Action, Proof, and Memory planes.
4. Approve the local overlay. The conclusion moves first without changing the public core.
5. Run local Verifiers. Check source preservation, public-core isolation, and rollback.
6. Create the KPR draft and review the Agent-extracted Claims. Correct wording only where it needs revision, then explicitly attest the reviewed meaning and scope. Correction remains independently provenance-tracked, but it is not an attestation prerequisite.
7. Inspect Decision Brief, Knowledge Diff, Provenance, Evidence, and raw JSON. Run privacy scan and submit.
8. Run the Knowledge Gate. Missing attestation or failed privacy proof would block this transition.
9. Ask the Maintainer-side Agent. Compare Know, Infer, and Unknown.
10. In Knowledge review, change any Claim decision, scope, rollout, rationale, or Claim-linked Verifier. The Maintainer—not the Agent—owns Accept, Modify, Narrow, Defer, Reject, and Request evidence; an unknown Verifier blocks Contract synthesis.
11. Review the Impact Map. Its predictions and confidence remain visibly distinct from evidence.
12. Approve the Integration Contract. Confirm the contributor patch and private trajectory are hidden.
13. Start Blind Reconstruction. The Project Agent returns a candidate but cannot call it complete.
14. Run Contract Verifiers. Try rollback, rebuild, then adopt as Maintainer.
15. Open the Failure Laboratory. Four isolated controls must pass without damaging the active KPR.

Explore Mode is available by using the left navigation and changing Claim decisions. Scripted Fallback walks the same concept without model output. Live Agent calls the single server-configured Provider.

Application-only walkthrough

Open the Global XYZ Agent and choose Show only the reference application. The Reference Application becomes the entire stage while the XYZ Agent remains available. Its Application workflow section exposes the next action from the same canonical flow above; it does not create a simplified parallel state. Use Show me where whenever the next action is unclear. The red animated arrow stays outside the target, never receives pointer input, and disappears when the assistant closes. Choose Return to full workbench at any time to inspect the complete KPR or Developer Workspace at the current state.

To inspect the Job Talk interaction lineage, choose Agent Demo or Daily News & Notes in the Reference Application Gallery. Open the Local or Global XYZ Agent and invoke one bounded user-side capability. The application records a checkpoint before changing the user realization. Verify the change, then choose Ask the XYZ Agent to form a KPR draft. The workbench opens the KPR knowledge-collaboration page immediately. Review the problem, expected behavior, acceptance criteria, evidence, provenance, limitations, and local realization diff while retaining the explicit boundary that local code is not project authority. Use Roll back this local change inside the change section to restore the exact prior realization; the dependent KPR draft is invalidated and the workbench returns to the User Workspace.

Switch among Research Brief, Agent Demo, and Daily News & Notes and inspect the contextual four-step preset above the right-side request. While the request is still a recognized system preset, the next application loads its own preset automatically. Edit the request, switch applications again, and confirm that the authored text is preserved. For Agent Demo and Daily News & Notes, choose Use this preset with the XYZ Agent, or write a request and choose Ask the XYZ Agent about this change. The proposal appears in the same right-side conversation and can be applied directly; the Local XYZ Agent does not open as a handoff. Open the Local XYZ Agent afterward to confirm that both entry points expose the same checkpoint and governed application state. Research Brief continues into the complete governed User-side Agent path.

Each Reference Application contains its own Local XYZ Agent. Open it inside the application and observe the visible Only this application boundary. Capability presets are inserted into the bottom conversation, where the user's instruction, the assistant's proposal, and the apply action remain in chronological order. Agent Demo and Daily News run their allowlisted reversible flow locally; Research Brief proceeds from a user need to its KPR handoff; Issue Triage and Release Desk explain their target maps without pretending to support mutations. Ask a Local XYZ Agent to switch applications, configure the Provider, or open the global Runtime and it refuses the out-of-scope request. Use the fixed outer Global XYZ Agent for those workbench-level operations.

Drag a Local XYZ Agent launcher to another position inside the current application. The launcher is clamped to that application even when the pointer moves outside it, does not open at the end of a drag, and remembers a separate position for each Reference Application. Focus the launcher and use the arrow keys for keyboard movement; hold Shift for a larger step. Press Home, or use Reset icon position inside the Local XYZ Agent panel, to restore the default.

Runtime is already open when the guided demo starts. It appears as a docked right sidebar and remains visible while switching User Workspace, KPR Bridge, or Developer Control Plane. Confirm that the Reference Application and User-side Agent stay side by side while the available width changes; they never reorder vertically. Application-only presentation hides the workbench Runtime and restores it when returning to the full workbench. Close Runtime only when the trace is no longer needed as working context.