tegwick b0f61b2d8b 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.		2026-07-29 23:15:42 +02:00
..
phase-001	Advance WP-0007: degeneration research, profile catalog, canonicalization checklist	2026-07-29 22:31:19 +02:00
pilot-candidates	Add info-tech-canon as first dry-run pilot candidate, exercise onboarding routine	2026-07-29 23:15:42 +02:00