Add info-tech-canon as first dry-run pilot candidate, exercise onboarding routine

Maintainer chose info-tech-canon (outside the original four product
lines) as the actual first repo to build up the practical
Phase-declaration routine on, explicitly confirmed as a dry run, not a
T05 go-live decision.

Adds a third draft, non-binding manifest
(examples/pilot-candidates/info-tech-canon-service-surface/): the
cumulative service surface across ITC-WP-0001-0012 (all finished),
Product-defining (100x). Flags a notable complication rather than
smoothing it over: this repo's current LICENSE is already MIT-0, so a
real Phase here would mean replacing an already-open license with
restricted pre-conversion TRSL terms - a materially different step
than the other two candidates.

Exercised the full onboarding routine end-to-end against a real,
ephemeral local instance of the hosted Trust Service (Docker Postgres,
migrations applied, binky Licensor token seeded, uvicorn running the
actual service/app.py): register-phase -> append-entry -> status all
worked via scripts/trf_onboard.py exactly as
specs/TrustServiceOnboarding.md describes, no code changes needed.
Dry-run infrastructure torn down afterward; only the draft manifest
files persist.

examples/pilot-candidates/README.md

@@ -16,14 +16,25 @@ Built from the two candidates identified with a defensible rationale in
 `helix-forge` produced no defensible candidate at survey time and are
 not represented here.
 
+**`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.
+of how complete or plausible these examples look — including
+`info-tech-canon`, which was explicitly confirmed as dry-run-only.
 
 | 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-0001`–`ITC-WP-0012` | Product-defining (100x) |
 
 All figures (`initial_target`, `target_basis`) are illustrative
 placeholders for this worked-example exercise, not a real costing or

examples/pilot-candidates/info-tech-canon-service-surface/ledger.json

@@ -0,0 +1 @@
+[]

examples/pilot-candidates/info-tech-canon-service-surface/manifest.json

@@ -0,0 +1,28 @@
+{
+  "framework": "TRF-0.1",
+  "license": "TRSL-0.1",
+  "phase": {
+    "id": "trsl:phase:draft-info-tech-canon-service-surface",
+    "milestone_release": {
+      "name": "info-tech-canon-service-surface-v1 (ITC-WP-0001..0012)",
+      "source_revision": "f7ad73d"
+    },
+    "initial_target": {
+      "amount": 2500000,
+      "currency": "EUR"
+    },
+    "target_basis": {
+      "estimated_effort_days": 25,
+      "daily_rate": 1000,
+      "approved_direct_costs": 0,
+      "target_multiple": 100
+    },
+    "future_license": "MIT",
+    "degeneration_policy": "trsl:policy:linear-longstop-v0@1.0",
+    "longstop_at": "2029-01-01T00:00:00Z",
+    "ledger": "examples/pilot-candidates/info-tech-canon-service-surface/ledger.json"
+  },
+  "extensions": [
+    "trsl:extension:development-license@1.0"
+  ]
+}