Milestone 1: Read-only factory graph

Last reconciled: 2026-10-10T18:55:12.191Z. Team: RUNNING. Milestone.

The synthetic graph is published, but operator review reopened visual acceptance. ELK Layered with orthogonal routing is now integrated in PR #14; actual application screenshots are available. Real input integration, attention and release acceptance remain ahead.

Stories describe outcomes; tickets are delivery containers. The mapping is many-to-many. Unticketed work, decisions and standing obligations are named explicitly. A landed enabler does not mean the product outcome is delivered.

Delivery map

Dependency-stage Gantt — not a calendar forecast. Each equal-width bar occupies one dependency stage; positions are calculated from the prerequisites below. Synthetic dates are rendering coordinates only. Widths are not effort, duration or completion percentages. Standing obligations are checkpoints. Same-stage rows may be independent, but this chart grants no dispatch authority.

Labels report delivery state; only in-progress rows use active colouring.

%%{init: {"gantt": {"leftPadding": 380, "sectionFontSize": 12, "fontSize": 12}}}%%
gantt
    title Milestone 1 Read-only factory graph - dependency stages
    dateFormat YYYY-MM-DD
    axisFormat Stage %j
    tickInterval 1day
    todayMarker off
    section Graph and attention
    Explore the complete factory graph [review] :explore-graph, 2025-01-01, 1d
    Copy evidence-backed repair prompts [planned] :attention-prompts, 2025-01-05, 1d
    section Private inputs
    Configure a private installation [planned] :private-configuration, 2025-01-02, 1d
    Observe GitHub work [planned] :github-records, 2025-01-03, 1d
    Observe local communication records [planned] :local-records, 2025-01-04, 1d
    section Release assurance
    Review privacy before release [planned] :release-evidence, 2025-01-06, 1d

State key: landed/delivered = evidence linked; review/ready = not landed; blocked/decision = unresolved prerequisite; planned = not commissioned; standing = continuing obligation.

Graph and attention

Story	Kind	Tracking	State	Owner
Explore the complete factory graph	product	Ticketed — #4, #10	review	Project owner
Copy evidence-backed repair prompts	product	Ticketed — #8, #10	planned	Project owner

Explore the complete factory graph

As a factory operator, I want to navigate and inspect work and role relationships without losing the global view, so that I can understand the recorded factory state.

Tracking: Ticketed. Child delivery ticket and parent epic; scope is the named capability. #4, #10.

Now — review: Functional and hosted checks passed, but operator review found unclear graph semantics and poor layout. PR #14 is draft again. The ELK integration at b1b9b83 has passed local checks; actual desktop/mobile screenshots document the implementation. Hosted checks and renewed operator visual acceptance are tracked on the PR.

Acceptance: Reviewed accessible graph with honest missing/stale states, passing local and hosted checks and a working preview.

Dependencies: No prerequisite story recorded; this is not dispatch authority.

Next: Integrate the selected layout and clearer semantics, then verify visual and interaction acceptance.

Evidence: Draft PR #14, Synthetic graph preview, Passing hosted checks, Layout review and algorithm decision

Copy evidence-backed repair prompts

As a factory operator, I want to find broken expectations and copy a prompt for a responsible role, so that I can resolve problems on the machine without diagnosing every graph detail.

Tracking: Ticketed. Child delivery ticket and parent epic; scope is the named capability. #8, #10.

Now — planned: Invariant candidates A-N and prompt contracts are merged. Runtime detection and prompt generation are not implemented.

Acceptance: Facts, unknowns, exceptions, evidence, authority-aware routing and shared-cause grouping tested through actual input boundaries.

Dependencies: Observe local communication records

Next: Implement graph-derived findings and manual prompts.

Evidence: No completion evidence claimed.

Private inputs

Story	Kind	Tracking	State	Owner
Configure a private installation	product	Ticketed — #5, #12	planned	Project owner
Observe GitHub work	product	Ticketed — #6, #11	planned	Project owner
Observe local communication records	product	Ticketed — #7, #11	planned	Project owner

Configure a private installation

As a factory operator, I want to choose permitted repositories and local files with private credentials, so that I can keep installation details and secrets out of public and browser data.

Tracking: Ticketed. Child delivery ticket and parent epic; scope is the named capability. #5, #12.

Now — planned: Configuration contract is documented; runtime configuration is not implemented.

Acceptance: Invalid or unsafe configuration refuses source activation with redacted diagnostics; no arbitrary discovery or external services.

Dependencies: Explore the complete factory graph

Next: Implement configuration after graph acceptance.

Evidence: No completion evidence claimed.

Observe GitHub work

As a factory operator, I want to read configured GitHub work into the graph, so that I can see milestones, issues and pull requests in context.

Tracking: Ticketed. Child delivery ticket and parent epic; scope is the named capability. #6, #11.

Now — planned: GitHub source adapter is not implemented.

Acceptance: Read-only configured access, provenance, freshness and honest unavailable states.

Dependencies: Configure a private installation

Next: Implement the GitHub reader.

Evidence: No completion evidence claimed.

Observe local communication records

As a factory operator, I want to read configured communication and status files through a public protocol, so that I can understand role obligations while worker implementations remain private.

Tracking: Ticketed. Child delivery ticket and parent epic; scope is the named capability. #7, #11.

Now — planned: Public protocol direction is documented; local reader is not implemented.

Acceptance: Strict decoding, explicit unsupported records and no local source writes.

Dependencies: Observe GitHub work

Next: Implement the configured local reader.

Evidence: No completion evidence claimed.

Release assurance

Story	Kind	Tracking	State	Owner
Review privacy before release	product	Ticketed — #9, #12	planned	Project owner

Review privacy before release

As a factory operator, I want to review the configured installation and its privacy evidence before release, so that I can run a trustworthy read-only dashboard.

Tracking: Ticketed. Child delivery ticket and parent epic; scope is the named capability. #9, #12.

Now — planned: No product release exists. Initial configuration review by the operator is still required.

Acceptance: End-to-end observation and privacy evidence accepted, actual configuration reviewed and release explicitly authorized.

Dependencies: Copy evidence-backed repair prompts

Next: Collect release evidence after the observation features.

Evidence: No completion evidence claimed.

Maintenance

This page and its Gantt are generated from the adjacent story register. The milestone owner must reconcile it on material state changes and before handoff. Updating the timestamp alone is not reconciliation. A normal debrief reads this page; an authorised state sweep updates and publishes it. If publication is blocked, the desk must name the stale publication and pending changes.

Register schema: milestone-stories/v1. Parsed-register SHA-256: 9f858169e272ba748f93ee8586df251bc02ebfd6a4b3aebe269fd13a414f90c3.