doclayer · how the demo works

The doc, born and shipped in one continuous reel.

• 0–10s · The architect proposes a trajectory of 4 articles. Atoms — title, contributors, scope, deploy target — snap into a manifest.
• 10–28s · Trajectory distributes into two work-windows. Vishal claims one lane, Akhil another. Each window is structurally different.
• 28–55s · Parallel drafting. Three AI agents fire from the middle column: research, adversarial, visual. Each surfaces inline augments in both lanes.
• 55–80s · Cross-collab handoff. Vishal completes a section; the architect packs it as a review packet; Akhil's harness reshapes around it.
• 80–105s · Single-article lifecycle zooms in: plan → draft → review → publish.
• 105–120s · Publish click. Build sequence runs. Reader-harness goes live; readers arrive with different priors; the page re-binds.

Empty workspace → grammar atoms snap into a layout.

• 0–3s · A blank form. Title, contributors, audience, deploy target. Four fields type themselves in.
• 3–4s · The architect composes a manifest. Atoms are emitted as a typed graph (each field becomes a node).
• 4–6s · Atoms snap into a layout. Outline, evidence panel, voice sampler appear in place — not because a template was picked, but because the manifest grammar bound them.
• 6–8s · The harness emerges. Topbar, harness-strip, status bar light up. The next phase chip ("plan") is highlighted on the lifecycle ribbon.

Evidence, owners, and unresolved holes before prose exists.

• 0–5s · The outline is a decision structure: every row has an owner, source requirement, or unresolved hole.
• 5–10s · Source cards bind to outline slots. The graph changes planning state without rewriting a paragraph.
• 10–16s · Akhil's objection becomes a section-order decision and evidence requirement, not review feedback.
• 16–22s · The plan locks only the claims with enough support and hands a clean set of holes to draft.

A blocked sentence opens continuations, then returns to writing.

• 0–6s · Rough drafting continues from the locked plan; the rail only shows continuation context.
• 6–10s · The next sentence goes blank. The harness changes intent without leaving the draft phase.
• 10–16s · Three typed continuation variants appear for the current paragraph.
• 16–20s · One continuation is accepted and swaps into the paragraph.
• 20–22s · A compact decision trace remains so review can inspect the route later.

Accept, reject, route, and gate the section for publish.

• 0–4s · Review chips bloom inside blocks. Broad rewrites are rejected; one precise claim edit is accepted.
• 4–8s · Dismissed and routed chips collapse into a section-scoped review packet.
• 8–12s · The packet becomes a rubric: name the intent transition, manifest delta, and return state.
• 12–16s · The revised block clears the approval gate.
• 16–22s · Comments resolve and the lifecycle ribbon moves toward publish-ready.

Preview cycles priors. One button ships to doclayer.live.

• 0–6s · Reader-harness preview cycles through three priors (novice / practitioner / researcher). Same atoms, three binds.
• 6–10s · Preflight checks tick green: voice fidelity, citation coverage, lesson-memory commit, build-target reachable.
• 10–12s · Publish click. Button pulses; the build sequence panel expands.
• 12–18s · Build steps stream: pack atoms → render manifest → emit reader-harness shell → deploy → warm CDN.
• 18–22s · Live state. Share URL appears; a copy-button flash hints the article is shipped.

The doc becomes the reader's harness.

• 0–5s · A single hero column with a prior switcher: novice / practitioner / researcher.
• 5–12s · The reader changes prior. The article re-binds sequentially — paragraphs, citations, callouts re-render in place from the same atoms.
• 12–18s · Money shot: the column expands into three parallel reader views side-by-side. Same atoms; three structurally different renders.
• 18–22s · Comments thread shows three readers asking three differently-pitched questions about the same atom — proof the harness is per-reader, not per-page.

In-the-moment view. 02–05 are slices of this.

• 0–5s · Two shells side-by-side. Vishal's shell is research-heavy; Akhil's is voice/density-heavy. Same document, different harnesses.
• 5–12s · Both authors type in different sections. Cursors don't collide; the harnesses don't share layout — they share grammar.
• 12–18s · Sync gutter between the two shells routes a cross-collab event: a comment from Akhil shows up in Vishal's review rail as a review packet.
• 18–22s · Density meter for §3.2 climbs as Akhil tightens. Both shells reflect the same chain state, expressed differently.

Series spine, two writer lanes, three AI agents.

• 0–4s · The series spine across the top — 4 articles, current article highlighted, others queued.
• 4–10s · Two writer lanes drop down from the spine. Each lane is a per-author task queue with its own intent state.
• 10–14s · Orchestration rail in the middle — the three AI agents (research, adversarial, visual). Pulses light up as agents fire.
• 14–18s · A research agent surfaces a citation into Vishal's lane. An adversarial agent flags a claim in Akhil's lane. A visual agent renders a diagram inline.
• 18–20s · Counter strip ticks: words, citations, lessons, sections approved. The shared spine state updates.
• 20–22s · The lanes thesis: the harness arranges the work, not just the chrome. Lanes are first-class.

One full protocol cycle, ~30 seconds, both sides visible.

• 0–4s · Vishal types §3.2 live. The AI inline-augments two clauses as he writes.
• 4–7s · Vishal pauses. The architect packs the section as a review packet — a "packet pip" flies across the gutter.
• 7–10s · Akhil's harness gets a notification. The intent state shifts: "incoming packet → review-mode".
• 10–17s · Akhil's harness reshapes: outline collapses, review rail expands, the packet is bound into the editor with full provenance.
• 17–22s · Akhil composes comments. A second packet — comments + dispositions — gets dispatched back.
• 22–26s · Vishal's harness receives the comments. Intent state shifts to "iterate-mode". His editor surfaces a diff rail.
• 26–30s · Vishal applies revisions. The loop closes. Both harnesses return to their original intents.