Software line¶
Software-specific workflow × inventory detail.
Tracking: Notion Workstreams database — view: Software Work. Gatekeeper: Engineering Lead. See agent setup.
L1 Delivery ladder¶
Frame → Design → Implement → Verify → Promote → Deploy → Document → (Operate handoff)
Software work is a workstream on an Initiative (usually software-as-product or an enabler for Editorial or Services). It may run concurrently with Product, Editorial, Services, or Operate workstreams.
Estate (not environments)¶
| Estate | Meaning |
|---|---|
| Prototype | Software sandbox: local git and abandonable. Not Product Explore. Not “dev”. |
| Lab | Promoted public showcase (hector-sanchez-eu). Not staging. |
| Portfolio-org | Promoted maintained app (Konstant-Ventures). Not production-as-env label; live runtime is Deploy + Operate. |
Estate (Prototype → Lab → Portfolio-org) is Portfolio/Software classify — not a Deploy inventory and not local/stage/prod.
Inventories by stage¶
| Stage | Inventories |
|---|---|
| Frame | app-kind, outcome (may bind from Product line) |
| Design | brand, design-approach, arch-checklist |
| Implement | build-blueprint, tech-stack |
| Verify | verify-profile |
| Promote | promote-target (Lab | Portfolio) |
| Deploy | host, shape |
| Document | doc-profile |
Host × shape (Deploy)¶
host.konstant(default),host.vercel,host.vps-legacy(migration only),host.gcp(stub)shape.static,shape.dynamic-socket,shape.dynamic-always-on
Templates: templates/deploy/<host>/<shape>/ (Conductor-owned).
Roles¶
Engineering Lead, Implementer, Platform Engineer — see docs/roles-and-tooling.md.
The stage order and inventory ownership are decided. Each stage still needs explicit entry criteria, exit evidence, allowed next stages, and rollback behavior before Conductor may authorize its transitions deterministically.
Cross-line coordination¶
- In: Portfolio may add Software directly; a Product build gate, Services delivery need, or Editorial tooling need may add or activate a Software workstream.
- Out: A verified Lab URL may activate an Editorial release workstream; a deployment may activate an Operate workstream.
- Evidence: Verify, release, and deploy results are linked to the Software workstream and may satisfy other workstream stage conditions.
Production system: GitHub repositories own source, branches, commits, PRs, checks, releases, and deployments. Notion owns the Initiative and Software workstream stage. GitHub issues are optional; GitHub Projects must not become the portfolio spine. See tooling-map.md.
Full zoom / binding rules¶
See historical detail in git history of this file if needed; runtime units live under corpus/lines/software/.