Interactive explanation

Can someone else continue this tomorrow?

A useful harness connects intent, work and evidence across sessions.

The conversation ends.
The decisions stay.

Conceptual artwork supplied by Johannes. The image is a metaphor, not product evidence.

IntentA fictional support knowledge assistant, with explicit outcomes and tenant boundaries.

Workflow and artifactsRequirements, design decisions, work map, review evidence and scoped lessons.

Client and modelTools, context, permissions and delegation vary by host. Validate the intended CLI or desktop app.

Platform and CIIdentity, access and deployment controls require their own configuration and verification.

This companion explains the method and replays verified local fixtures. It does not execute a model or configure a customer environment.

Demo 1 · Profile resolution

Same brief. Different acceptance bar.

Build a support knowledge assistant from synthetic documents.

Real Lintel resolver, synthetic packs. The custom demo_policy fields are defined for this presentation.

The downstream decision

Prepared contract comparison. A pack value alone does not provision or enforce anything.

01Effective profile

02Requirement

03Design decision

04Executable check

Which decision should change for your customer?

Open recorded helper assertions

Demo 2 · Cold reconstruction

Continue without the previous chat.

The local demo commits the durable artifacts and reads them from a fresh local clone.

What this proves

Reading and validating the map is mechanical. Correct model interpretation needs a real-client rehearsal.

What is the minimum evidence your colleague needs?

Open recorded cold-start assertions

Demo 3 · A scoped lesson and a regression

The happy path can hide a boundary failure.

Retrieve a support document within the caller’s tenant.

Code excerpts explain the fixture. See demo/ for the executed implementation.

Same contract tests

Tenant identity is assumed trusted in this fixture. Production authentication and authorization need separate verification.

OBSERVECross-tenant leak

REVIEWScope the correction

CAPTURERecord the rule

RETRIEVEFind it on the next task

VERIFYRerun the regression

When should this lesson be changed or retired?

Open recorded learning assertions

Optional five-minute extension · Topology simulation

Coordinate before fan-out.

One work map. Bounded ownership. Review before integration.

Interactive design explanation only. No worker, worktree or commit is created here. Swarming source snapshot: 275a354.

A worker must not approve its own change. Same-wave writes require isolated, attributable changes. A lane review does not replace final integration review.