Workstreams¶
The detail — one row per active line contribution. Linked to Initiatives. Updated by agents as stages advance.
| Initiative | Line | Stage | Estate | Evidence | Next action |
|---|---|---|---|---|---|
| Example: Survey Automation Platform | Portfolio | Capacity | — | WIP slot available | Review Aug 15 |
| Example: Survey Automation Platform | Product | Explore | — | 3 buyer interviews, desk research complete | Score by Aug 1 |
| Example: Gmail Curator | Portfolio | Review | — | All workstreams active, metrics green | Next review Sep 1 |
| Example: Gmail Curator | Software | Deploy | Lab | Health checks passing, live URL verified | Document setup |
| Example: Gmail Curator | Operate | Run | — | SLO green, metrics nominal | Review weekly |
| Example: Gmail Curator | Editorial | Publish | — | Release piece staged, fact-checked | Publish to hectorsanchez.eu |
| Example: Germany Temperature Trends | Portfolio | Review | — | Editorial workstream active | Review monthly |
| Example: Germany Temperature Trends | Editorial | Publish | — | Staged, locales verified | Publish, then Update |
| Example: AI Tool Evaluation Report | Portfolio | Review | — | Services engagement active | Review monthly |
| Example: AI Tool Evaluation Report | Services | Deliver | — | Report draft complete, client review pending | Incorporate feedback, finalize |
How to update¶
When a workstream advances:
- Update
Stageto the new stage - Add
Evidence— what was produced or verified - Set
Next action— concrete, specific, dated if possible - If the workstream completes, remove the row (it moves to the Initiative's history)
Estate¶
Estate applies only to Software workstreams. It is set during Product Build-gate:
- Prototype — local git only, no deploy, no CI/CD
- Lab — hector-sanchez-eu, deployed to konstant, catalog entry
- Portfolio-org — Konstant-Ventures, own website, commercial
See estate chooser for decision rules.