coulomb/target-revenue
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(consistency): sync task status from DB [auto]

Browse source 
Updated by fix-consistency on 2026-08-05:
  - update .custodian-brief.md for target-revenue
This commit is contained in:
custodian-sync 2026-08-05 15:59:58 +02:00
parent fdb59efbc3
commit f56d82f09a
8 changed files with 200 additions and 121 deletions
Download patch file Download diff file Expand all files Collapse all files

42
examples/pilot-candidates/README.md
View file

@ -1,34 +1,22 @@
# Pilot candidate Phase Manifests — DRAFT, NOT DECLARED
# Pilot candidate Phase Manifests
These manifests are **draft, non-binding worked examples**
(`workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T03), following
the pattern established by `examples/phase-001/`. They are structurally
valid and conformance-tested exactly like `examples/phase-001/`, but:
These manifests began as **draft, non-binding worked examples**
(`workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T03). They keep
a `draft-` phase id prefix so they are never confused with a declared
Phase.
- **No Commercial Entitlement is for sale under either manifest.**
- **No Development Credit is being tracked for either candidate.**
- **Neither repo's actual License header has been changed to TRSL.**
- `phase.id` uses a `draft-` prefix specifically so it cannot be confused
with a real, declared Phase.
**Go-live 2026-08-05:** T05 accepted the first **real** Phase for
`info-tech-canon` — the authoritative declaration lives in that repo at
`trf/phase-service-surface.json` as
`trsl:phase:info-tech-canon-service-surface` (not the draft file here).
Full record: `history/260805-T05-GoLive-info-tech-canon.md`.
Built from the two candidates identified with a defensible rationale in
`specs/PilotPhaseCandidateSurvey.md` (T02) — `coulomb-loop` and
`helix-forge` produced no defensible candidate at survey time and are
not represented here.
The draft directories below remain as historical worked examples for
candidates that are **not** yet declared:
**`info-tech-canon` (2026-07-29):** the maintainer chose `info-tech-canon`
as the actual first repo to build up the practical Phase-declaration
routine on, explicitly as a **dry run, not a go-live decision**
(confirmed directly, not assumed) — see
`specs/PilotPhaseCandidateSurvey.md` §5 for the candidate rationale. This
repo was outside the original four product lines T02 surveyed; its
candidate was added afterward as this specific, real routine-building
exercise, not a T02 survey gap.
**Nothing here is authorized to go live.** That remains gated behind
`workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T05, regardless
of how complete or plausible these examples look — including
`info-tech-canon`, which was explicitly confirmed as dry-run-only.
- **No Commercial Entitlement is for sale under the draft manifests.**
- **`net-kingdom` and `railiance-vergabe-teilnahme` drafts are still not
declared** — T05 authorized only the info-tech-canon Phase.
| Directory | Product line | Candidate deliverable | Indicative Target Multiple |
|---|---|---|---|