target-revenue/examples/pilot-candidates
custodian-sync f56d82f09a chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-08-05:
  - update .custodian-brief.md for target-revenue
2026-08-05 15:59:58 +02:00
..
info-tech-canon-service-surface Implement WP-0015-T01/T04/T06: Phase provenance schema + ledger UI 2026-08-03 20:43:30 +02:00
net-kingdom-local-identity Implement WP-0015-T01/T04/T06: Phase provenance schema + ledger UI 2026-08-03 20:43:30 +02:00
railiance-vergabe-teilnahme Implement WP-0015-T01/T04/T06: Phase provenance schema + ledger UI 2026-08-03 20:43:30 +02:00
README.md chore(consistency): sync task status from DB [auto] 2026-08-05 15:59:58 +02:00

Pilot candidate Phase Manifests

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.

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.

The draft directories below remain as historical worked examples for candidates that are not yet declared:

  • 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
net-kingdom-local-identity/ net-kingdom NK-WP-0002 Local Identity Incremental (10x)
railiance-vergabe-teilnahme/ railiance-* (railiance-apps) vergabe-teilnahme (RAILIANCE-WP-0002/-0014) Product-defining (100x)
info-tech-canon-service-surface/ info-tech-canon Cumulative service surface, ITC-WP-0001ITC-WP-0012 Product-defining (100x)

target_basis/initial_target figures (updated 2026-07-30): all three now use target_revenue.effort_calculator-derived values (workplans/TREV-WP-0010-development-effort-calculator.md T03), not the originally hand-picked illustrative placeholders. Full derivation, warnings, and the judgment calls involved (date-scoping, and which of two repos to measure for railiance-vergabe-teilnahme) are in history/260730-EffortCalculator-CandidateApplication.md. Two of the three carry explicit calculator warnings recommending a manual override before any real use — these are still draft, non-binding figures, not a settled costing proposal. See specs/PilotPhaseCandidateSurvey.md for the underlying candidate rationale (unaffected by this figure update).