T01: specs/TRSL-Governance.md. Resolves the Licensor-identity question (maintainer decision, 2026-07-29): a single shared Licensor, Binky Hedgehog GmbH, operating as the binky tenant, across all four product lines - not per-product-line. Unblocks (does not itself resolve) the License/CUA arbitral-institution selection now that the Licensor's own jurisdiction is known. Tables versioning/extension-governance/operator- governance status per concept §20, naming open items (compatibility rules, deprecation criteria, conflict-of-interest rule, key-rotation history) rather than silently assuming them solved. T02: specs/PilotPhaseCandidateSurvey.md. Direct repo inspection (hub had no goal data for three of four product lines) plus an Explore-agent survey of all ten railiance-* repos. Two defensible candidates found: NK-WP-0002 Local Identity (net-kingdom, Incremental 10x) and vergabe-teilnahme (railiance-apps, Product-defining 100x, the only genuinely product-shaped deliverable across ten railiance-* repos). coulomb-loop and helix-forge have no candidate, for stated principled reasons (internal tooling; pre-implementation-stage, respectively). T03: examples/pilot-candidates/ - draft, non-binding Phase Manifests for both real candidates, trsl:phase:draft-* ids, empty ledgers, schema-validated, explicit README stating nothing here is authorized to go live. T04: specs/TRSL-ContributorLicenseAgreement-Draft.md, implementing the CLA-not-assignment recommendation from history/260729-TRSL-ContributorRights-Research.md - narrowly scoped to the current Phase's TRSL terms plus its already-declared Future License at Conversion, same preliminary-candidate treatment as the License/CUA V1C1 documents. CONTRIBUTING.md updated to point at it while keeping the external-contribution block in effect until accepted. T05's precondition list updated to reflect what's now resolved, still left todo by design pending the maintainer's own go-live decision. |
||
|---|---|---|
| .. | ||
| net-kingdom-local-identity | ||
| railiance-vergabe-teilnahme | ||
| README.md | ||
Pilot candidate Phase Manifests — DRAFT, NOT DECLARED
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:
- 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.iduses adraft-prefix specifically so it cannot be confused with a real, declared Phase.
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.
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.
| 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) |
All figures (initial_target, target_basis) are illustrative
placeholders for this worked-example exercise, not a real costing or
pricing proposal — see specs/PilotPhaseCandidateSurvey.md for the
underlying candidate rationale.