Review the exact publication scope before a branch or pull request is represented as external state.
3 of 7 work items have adjacent evidence
Buildout · Visual Language · specimen data
ActiveForeman project workbench
Ship the first high-fidelity Foreman project, buildout board, and selected-buildout workbench without inventing runtime behaviour.
3 of 7 work items have adjacent evidence
Current stepCompose the selected-buildout workbench and responsive inspector.
Work items7
Sessions3
ProvidersKimi CLI · ChatGPT Web · GitHub
These controls are static review specimens. They do not resume a session, grant authority, send a handoff, or mutate GitHub.
Human attention
The blocked transition and safe decision share one view.
Active
Work items
Bounded tasks retain owners, outputs, and evidence.
A completed label is not shown without adjacent completion evidence.
| Work item | Owner | State | Expected output | Evidence and next action |
|---|---|---|---|---|
| Create attributable specimen data | Builder agent | Completed | Frozen project, buildout, work-item, session, approval, artifact, and activity records. | Fixture contract exposes distinct identities and state families. Next · Inspect the generated views. |
| Design the project index | Builder agent | Completed | A project chooser with active work, attention, repository context, and recent movement. | The project route identifies owner, active buildouts, attention, and repository before navigation. Next · Review narrow-screen hierarchy. |
| Design the buildout board | Builder agent | Active | Lifecycle columns with provider and session attribution and no colour-only state. | Current specimen shows active, waiting, degraded, failed, cancelled, and completed work. Next · Finish responsive collapse. |
| Compose selected-buildout workbench | Builder agent | Active | One view containing goal, work, sessions, approvals, artifacts, GitHub projection, activity, and inspector. | The workbench uses shared v2 workbench regions and semantic tokens. Next · Review evidence adjacency. |
| Audit compact layouts | Reviewer agent | Blocked | Keyboard and 1120, 820, 640, 390, and 320 pixel review evidence. | Structural rules are present; screenshot evidence is not represented in this static fixture. Next · Run the final screenshot review. |
| Publish the implementation branch | Chris person | Waiting for approval | One exact branch and one draft pull request for issue #36. | No external mutation is claimed by this specimen. Next · Review the approval scope. |
| Close issue after verified merge | Reviewer agent | Proposed | Issue #36 closed only after merged code and validation are read back from GitHub. | Issue remains open in the specimen. Next · Wait for merge evidence. |
Sessions
Provider, connection, agent, and session stay distinct.
Desired and actual state appear together. No session is merged merely because it contributes to the same buildout.
Kimi CLI · Foreman #36
Compose selected-buildout workbench
- Agent
- Builder · agent
- Connection
- connection-kimi-cli
- Desired
- active
- Observed
- active
- Last activity
ChatGPT Web · design review
Review evidence adjacency
- Agent
- Reviewer · agent
- Connection
- connection-chatgpt-web
- Desired
- available
- Observed
- idle
- Last activity
GitHub · issue projection
Observe issue #36
- Agent
- GitHub · external authority
- Connection
- connection-github
- Desired
- ready
- Observed
- ready
- Last activity
Approvals
Authority is exact, expiring, and separate from execution.
Publish one issue-scoped branch
- Requester
- Builder · agent
- Decision owner
- Chris
- Scope
- Write one branch for issue #36 and open one draft pull request targeting main.
- Consequence
- Repository collaborators can inspect the proposed Foreman screens and tests.
- Not included
- Merge, release, deployment, credential changes, and unrelated repository writes.
- Expires
Artifacts and GitHub projection
Outputs preserve producer, ancestry, and availability.
Project laboratory fixture
Issue #36 → fixture model
- Producer
- Builder
- Evidence
- Static source artifact; not a runtime record.
Selected buildout route
Issue #36 → workbench composition
- Producer
- Builder
- Evidence
- Available only after the branch source is inspected.
Responsive screenshot set
Issue #36 → final validation
- Producer
- Reviewer
- Evidence
- Not yet represented as completed evidence.
Project and buildout workbench laboratory
Issue observed; no publication result is asserted by the specimen
- Requested effect
- Publish an issue-scoped branch and draft pull request
- Verification
- Canonical branch and pull-request read-back is required before showing verified publication.
Activity
Actor, event, affected object, and evidence remain attributable.
- Composed distinct project, buildout, session, approval, artifact, and activity records.
Builder · agent · Foreman project workbench
Evidence · Fixture contract - Confirmed the design consumes shared v2 tokens and workbench regions.
Reviewer · agent · Visual contract
Evidence · Component and workflow catalogue - Continued the selected-buildout composition and compact inspector layout.
Builder · agent · Selected buildout route
Evidence · Current specimen source - Publication remains a separate human decision with an exact scope.
Chris · person · GitHub publication request
Evidence · Pending approval record