Skip to content

3bd8f5b6.md

Latest commit

 

History

History
95 lines (70 loc) · 4.91 KB

3bd8f5b6.md

File metadata and controls

95 lines (70 loc) · 4.91 KB
Raw
uid 3bd8f5b6
title build — dev-pipeline stage
type pipeline
subtype workflow-node
name build
version 1.1.0
author argus-a42
owner argus
modified_by argus-a49
modified 2026-05-07
status draft
state active
role stage
children
24f16afc
9d4f7e21
next_steps
3a7dbdda
relationships
rel uid
member_of
cd1fcd25
schema_version 2
extraction_scope ship
member_of
subsystem_hub
76bab75f
capsule_version 2.5

build — dev-pipeline stage

📍 Vault Path: tropo-subsystems → Tropo Playbooks → build — dev-pipeline stage

🔗 This file — UID 3bd8f5b6 · type pipeline · state active · status draft

📥 Cited by (1):

Purpose

The build stage executes the arch-specs produced by specify, then auto-fires hub release_history derivation per Rule 12. For each arch-spec, the agent authors three artifacts (research node, sprint plans with testing plans, documentation node). After all arch-specs are artifacts-complete, the executor fires update-subsystem-canonical-docs (v1.9.2 NEW) which writes hub release_history rows + last_release_reflected bumps + subsystem-registry rows from the release-plan's capabilities_touched: + hub_summaries:.

Does NOT govern: spawning the arch-specs themselves (that is specify stage territory), or producing the deployable artifact and release notes (that is deploy stage territory).

Structure

build (3bd8f5b6)
├── step-3: author-arch-spec-artifacts (24f16afc)
└── step-4: update-subsystem-canonical-docs (9d4f7e21) — NEW v1.9.2 Stream A4

Flow: linear two-step chain. Build is complete when step-4 completes.

Nodes

UID Name Role Children Next Steps
24f16afc author-arch-spec-artifacts step 0 [9d4f7e21]
9d4f7e21 update-subsystem-canonical-docs step 0 []

Flow Rules

Linear chain. Step-3 advances to step-4 on completion via next_steps: [9d4f7e21]. Step-4 is terminal within build stage; on its completion, execution advances to deploy (3a7dbdda) via this stage's next_steps:.

Build may be iterative internally — an arch-spec's sprint plans may span multiple working sessions — but from the pipeline's perspective, step-3 is not complete until ALL arch-specs declared in the release-plan have their full artifact sets. Step-4 fires after step-3 closes.

Cold-Boot Walk-Through

A pipeline-run enters build with a committed release-plan and N arch-spec instances (one per declared sub-system).

Step-3 processes each arch-spec in turn: (a) authors a research node capturing relevant context and prior art, (b) authors one or more sprint plans each with a testing plan, (c) authors a documentation node updating the tropo-subsystems master documentation. When all N arch-specs are fully artifacts-complete, step-3 is done and step-4 begins.

Step-4 (v1.9.2 NEW) fires update-subsystem-canonical-docs. The executor reads the release-plan's capabilities_touched: and hub_summaries:, derives subsystems_touched: via 1-hop member_of: traversal, and for each touched hub: appends release_history: row, bumps last_release_reflected:, writes subsystem-registry row. Frontmatter only — body sections (## Change Log, ## Current State) are NOT written by this step (Q7 walk reframe; carry-forward note 4b7a9d3f files broader audience-split thesis for v1.10+). On step-4 completion, build stage advances to deploy.

Known Enforcement Gaps

Gap What closes it Target release Owner
No sprint-plan capsule type exists — step-3 references sprint plans as first-class artifacts Author sprint-plan.capsule alongside arch-spec.capsule design in v1.4.4 specify v1.4.4 argus
"All arch-specs complete" condition is not expressible as a single pipeline step — step-3 is effectively a loop over N arch-specs pipeline.capsule v2.1 iteration/loop semantics; at v1.0.0 this is hand-executed by the agent v2.1 argus

Changelog

Version Date Change Author
1.0.0 2026-05-03 Initial draft. Single step: author-arch-spec-artifacts. argus-a42
1.1.0 2026-05-07 v1.9.2 Stream A4 amendment. Added child step update-subsystem-canonical-docs (9d4f7e21) — auto-fires Rule 12 hub release_history derivation per v1.9.2 brief e7a3b591. children: [24f16afc, 9d4f7e21]; step-3 next_steps: [9d4f7e21]; step-4 terminal in stage; stage next_steps: [3a7dbdda] unchanged. Closes the manual-substitute pattern v1.8 + v1.9.0 + v1.9.1. UID preserved; structural edit per pipeline.capsule Rule 3 triggered minor version bump. argus-a49

build | stage WorkflowNode | dev-pipeline (cd1fcd25) | argus-a42 | 2026-05-03