archive and governance workbench
Export one transcript, then open a local archive workbench.
AgentExport keeps the front door honest:
run scaffold and connectors, export one HTML receipt, then publish the archive shell.
This companion page exists to lower orientation cost after that:
show the result, point at the proof, then open the right lane.
Pages is a companion docs surface. The primary surface remains the quickstart path.
Published shelf note:
the latest release is the frozen public packet,
while this Pages surface may move ahead with repository-side truth on main.
at a glance
- First success
scaffold+connectors-> HTML receipt -> archive shell- First proof
- one HTML transcript receipt plus one archive shell entrypoint
- Optional visual pass
- watch the promo reel only when it orients you faster
- Boundary
- local-first proof surface, not a hosted runtime
what you should see
Read the artifacts first, then open the explanations.
The first useful question is not “what architecture does this imply?” It is “what concrete thing should appear after the shortest truthful path runs?”
artifact 01
One HTML transcript receipt
You should get a browsable local receipt instead of a hidden export file or a promise about what the repo could do later.
artifact 02
One archive shell entrypoint
You should then get a local archive shell that routes transcript receipts, reports, and evidence on the same desk.
proof rule
Companion lanes stay after the proof
Promo, launch, integration, and governance all matter, but none of them should outrun the first visible artifacts.
visual walkthrough
Take the 20-second pass only when it helps you orient faster.
The promo reel is a compact visual companion for first-time reviewers. It does not replace the CLI quickstart or the archive shell proof. It exists to lower orientation cost before you run the real path.
share-ready asset
Social card
Need a single-frame preview for a post, chat share, or reviewer packet? Use the social card image.
distribution-prep
Launch kit
Once the product story and first visible proof are already clear, open the launch kit for share-ready copy and asset routing.
front door rule
Start with the shortest truthful path, then disclose the rest.
Think of the product like a workshop. First you turn on the bench light, then you test one tool, and only after that do you open the cabinets. That is why the opening route stays fixed: CLI quickstart first, archive shell proof second, secondary lanes after that.
Primary
CLI quickstart
The main door proves the product can actually run, not just describe itself.
First visible proof
Archive shell proof
The proof page explains what the local workbench already organizes and what it still must not overclaim.
Progressive disclosure
Open the next lane only when you need it
Reports shell, integration evidence, and governance stay visible, but they do not compete for the first screen.
first success path
Three steps to a real local receipt.
If you only want to answer “is this worth trying once?”, do not read every lane first. Run these three steps, in order, and let the product prove itself.
Read the bench shape
See the local workbench structure before you point the repo at a real transcript.
cargo run -- scaffold
cargo run -- connectorsYou confirm the workspace shape and the current connector surface.
Export one HTML transcript
Create one browsable receipt instead of guessing what the output will look like.
cargo run -- export codex \
--thread-id <thread-id> \
--format html \
--destination workspace-conversations \
--workspace-root /absolute/path/to/repoThe result is an inspectable HTML receipt inside .agents/Conversations/.
Publish the archive shell
Organize transcript, reports, and evidence into one local navigation surface.
cargo run -- publish archive-index --workspace-root /absolute/path/to/repoNow you have .agents/Conversations/index.html as the archive shell entrypoint.
you will get
Concrete artifacts, not abstract readiness.
- one HTML transcript receipt
- one archive shell entrypoint that links transcripts, reports, and evidence
- one reproducible local path from export to archive browsing
this does not mean
Proof is still not platform theatre.
- not a hosted archive platform
- not a live multi-user service
- not already
submit-ready - not already
listed-liveacross every secondary lane
proof ladder
Read the product in three increasing layers of confidence.
L1
CLI front door
The CLI can walk a new visitor through the truthful first path.
L2
Transcript receipt
Transcript export leaves behind a browsable HTML receipt, not just a hidden file.
L3
Archive shell
The archive shell organizes the local workbench into one navigable surface with clear side lanes.
open the right next door
Use progressive disclosure instead of opening every cabinet at once.
Archive shell proof
Open this when you want the shortest public explanation of what the archive shell proves and what it still must not claim.
Repo map
Open this when you already understand the product sentence and now need to know where files, lanes, and shells live.
Secondary packet and listing ledger
Use this only when lane truth matters. Packet and listing status belong in the second ring, not the first screen.
Latest release shelf
Use the release shelf when you need the newest tagged packet rather than the newest repository-side wording on main.
Release Shelf Truth
published shelf
Use the latest release when you need the newest published packet.
- tagged release notes
- the frozen packet links for that tag
- release notes for the shipped cut
- the packet state already frozen into a release
repository-side truth
Use the repo front door and Pages docs when you need the newest repository-side truth on main.
- front-door wording and CTA order
- packet and lane truth that moved after the last tag
- docs or governance hardening not yet republished
These are neighboring shelves, not the same shelf.
A newer main can sharpen wording and proof hierarchy before the next release is cut.