ArchDocs
Start free

Pick up where the last session stopped

Resume a task with its decisions, open questions and history in view. Each design doc keeps a work log with a handoff of what was done, what is blocked and what comes next, and task context labels each record by how current and how authorized it is.

Early access
Start freeCompare plans

Plans: Work logs come with design docs on every plan, in early access. Task context is on Team, Business and Enterprise.

DD-0021 · Shorter tender window for API carriersWork log

Work log

  1. E-3Person-reported

    Priya Raman

    Per-channel tender window merged in #482

    a41c9e2 · Found on GitHub

  2. E-4Agent-reported

    Claude Code run by Priya Raman

    Left a handoff for the next session.

Current handoff

From E-4

Left by Claude Code run by Priya Raman

Agent-reported
Done
Per-channel tender window, #482 merged.
Blocked on
Late acceptance handling waits on Q1.
Next
Confirm the Carrier Gateway change, then get Q1 answered by Maya Chen.

Channel tag in Carrier Gateway marked done by the agent. No change recorded for it yet; confirm next.

Plan tasks

2 of 3 checked in the Implementation plan

Open questions

Q1 · What happens when a carrier accepts after the window closes?

Copy resume prompt

Session 2 starts here

Resumes from E-4

Done: Per-channel tender window, #482 merged.

Blocked on: Late acceptance handling waits on Q1.

Next: Confirm the Carrier Gateway change, then get Q1 answered by Maya Chen.

Current
DD-0021: Approved by a person; ADR-0003
In progress
DD-0021 plans to change Carrier Gateway, not yet recorded as done
Uncertain

ADR-0004 · Queue late acceptances for re-offer

UncertainWritten by an agentProposed, not approved
Historical
ADR-0002 Lineage
Two sessions, one recordRecreated from Archdocs views with sample data.

Resume from the last handoff

Read Done, Blocked on and Next in the design doc work log.

Find the records for a task

Group linked decisions, open questions and history by their relationship to the work.

Judge the context before using it

Read currency and approval as separate labels, with partial coverage stated.

Hand off between sessions

Entries in the work log are marked Person-reported or Agent-reported. The Current handoff keeps Done, Blocked on and Next together. Copy resume prompt carries that context into the next session.

Cited commits are checked against GitHub when Archdocs can read the repository.

Agents read context over MCP before they start and leave a handoff when they stop. Explore MCP capabilities

Plans: Work logs come with design docs on every plan, in early access. Task context is on Team, Business and Enterprise.

Start with the relevant records

Supply a task, a repository and paths, and an optional design doc. The results group Current, Uncertain and Related records, Open questions, In progress work, Acceptance criteria, History and records found by text search.

Context page: records linked to the task

Context

Task
Shorten the tender window for API carriers
Repository (owner/repo)
lanefold/dispatch

Scope: DD-0021 and lanefold/dispatch

Current

  • DD-0021 · Shorter tender window for API carriers

    CurrentApproved by a person

  • ADR-0003 · Prefer carrier REST APIs over EDI where available

    CurrentApproved by a person

Related

  • Carrier Gateway

    RelatedVia a dependency

Open questions

  • Q1 · What happens when a carrier accepts after the window closes?

    Assigned to Maya Chen

In progress

  • DD-0021 · Shorter tender window for API carriers

    In progress

    DD-0021 plans to change Carrier Gateway, not yet recorded as done

Uncertain

  • ADR-0004 · Queue late acceptances for re-offer

    UncertainWritten by an agentProposed, not approved

History

  • ADR-0002 · Tender loads over EDI 204 before carrier APIs

    HistoricalLineage

Records you cannot open are not shown.

Context assembled from linked recordsRecreated from Archdocs views with sample data.

Know how much to rely on each record

Current means directly linked and either approved by a person or, for a canvas doc, fresh; nothing recorded says it no longer applies. Related means connected indirectly. Uncertain needs confirmation and says why. Historical is background. None of these says the record governs your task, and none says the implementation matches.

Approval is shown separately. None of these labels says the implementation matches. Verified appears only on an acceptance criterion whose evidence was accepted under your policy.

Full record label legend
Current
Directly linked to the task, and either approved by a person with nothing superseding it and no open amendment, or, for a canvas doc, updated recently enough to count as fresh. It doesn’t mean the record governs your change.
Related
Connected through a dependency or the same repository rather than linked directly.
Uncertain
Found only by text search, or linked but not approved, written by an agent, or of unknown or stale freshness.
Historical
Superseded, abandoned, deprecated or rejected; kept for background.
Approved by a person
A person reviewed and approved the record.
Ready, not reviewed
Ready for use, without a recorded review.
Written by an agent
The text was written by an agent.
Documented, not approved
A choice is recorded without approval.
Via a dependency
Found through a recorded dependency.
Same repository
Linked to the repository supplied for the task.
Lineage
Connected through the history of an earlier or replacement record.

Code locations

Owners map repository paths to objects and docs. A task touching those paths finds the linked records. Paths that do not match are reported.

Access and limits

Records you can’t open are left out. Partial coverage is stated. Context comes from linked records, not from reading code.

Screenshots are from a sample workspace. Recreated views are labeled.

Start freeCompare plansExplore Design DocsRead the docs