proof, not platform theatre

Use this page to understand what the archive shell really proves before you assign it more authority than it has earned.

The archive shell proof is the first public explanation layer after the CLI front door. It shows that transcript export, report routing, and governance evidence can already be organized into one inspectable reading surface. It does not turn the repo into a hosted product or a live remote service.

Back to GitHub front door Open repo map Return to docs home

what this page is for

Audience
a first-time reviewer trying to separate proof from overclaim
Main question
What does the archive shell already prove today?
Boundary
local workbench proof, not a hosted runtime

what you should see

Read the artifacts first, then use diagrams as map legends.

Before this page earns the right to show diagrams, it should tell you what concrete things the shortest truthful path is supposed to leave behind.

artifact 01

One HTML transcript receipt

You should get a browsable transcript receipt inside .agents/Conversations/, not just a hidden export file.

artifact 02

One archive shell entrypoint

You should then get .agents/Conversations/index.html as the local navigation surface for transcripts, reports, and evidence.

proof boundary

Still local-only proof

Those artifacts prove a local workbench path. They still do not prove a hosted runtime, a remote service, or a live app shell.

visual proof assets

Two diagrams, two jobs.

The first diagram shows the workbench shape. The second shows the proof ladder from CLI to transcript receipt to archive shell. Read them like map legends after the artifacts, not like a product hype montage.

AgentExport archive shell proof diagram
Archive shell proof map: how transcripts, retrieval receipts, and governance evidence sit on the same local desk.
AgentExport proof ladder from CLI to transcript receipt to archive shell
Proof ladder: the order in which confidence should increase.

what this proof actually shows

Real local workbench proof.

  • transcript export can become a browsable HTML receipt
  • publish archive-index can organize transcripts, reports shell, and integration evidence into one inspectable archive shell
  • the archive shell is already workbench proof: it can route a reader through local artifacts without pretending to be a hosted platform

what this proof does not show

Do not promote proof into product theatre.

  • this is not a hosted product demo
  • this is not a GitHub Pages live archive shell
  • this is not a remote multi-user platform
  • this does not automatically mean submit-ready, listed-live, or already approved

how to reproduce it locally

Three commands, one honest result.

Treat this like checking a lab result for yourself. Do not trust the diagram alone; run the path and inspect the artifacts it leaves behind.

01

Confirm source availability

cargo run -- connectors

You confirm which transcript sources are actually available before you export anything.

02

Export one HTML transcript

cargo run -- export codex \
  --thread-id <thread-id> \
  --format html \
  --destination workspace-conversations \
  --workspace-root /absolute/path/to/repo

This leaves behind a concrete HTML receipt in .agents/Conversations/.

03

Publish the archive shell

cargo run -- publish archive-index --workspace-root /absolute/path/to/repo

Now the transcript, reports shell, and integration evidence can be browsed as one local navigation surface.

After a successful local run you should see .agents/Conversations/*.html, .agents/Conversations/index.html, and navigation paths from the transcript browser into reports shell and integration evidence.

proof ladder

Confidence should climb in order.

L1

CLI front door

The CLI can export a transcript through the truthful front door path.

L2

Transcript receipt

The export leaves a browsable HTML receipt rather than a hidden one-off file.

L3

Archive shell

The archive shell organizes transcript, reports, and evidence into one navigable local surface.

next doors

After proof, choose the right frozen or reviewer-facing shelf.

This page explains what the archive shell proves. Once that question is answered, the next question is usually one of four: do you need the visual companion, the launch kit, the latest published packet, or the wider packet/listing ledger?

visual companion

Promo reel

Use this when you want the shortest visual walkthrough before you open the proof or quickstart layers in detail.

Open promo reel

distribution-prep

Launch kit

Use this when the product story is already clear and you need truthful share-ready copy, asset routing, and packet-prep guidance.

Open launch kit

Published shelf

Latest release

Use this when you need the newest frozen public packet rather than the newest repository-side wording on main.

Open latest release

Packet truth

Distribution packet ledger

Use the ledger when you need platform/listing status, not when you are still trying to understand the product itself.

Open packet ledger

when to open this page

You need a proof explanation, not a product tour.

Open this page when someone needs to understand the current proof boundary before evaluating reports shell, integration evidence, or governance lanes.

why this matters

Truthful product positioning depends on ordering.

AgentExport is already more than an export utility, but its first public proof still has to start with CLI quickstart, transcript export, and archive shell generation.