target-revenue/history/260805-T05-GoLive-info-tech-canon.md

# WP-0008-T05 Go-Live — first real Phase: info-tech-canon

**Date:** 2026-08-05  
**Decision:** Maintainer accepted `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T05.  
**First declared Phase:** `trsl:phase:info-tech-canon-service-surface`  
**Declaring repo:** `coulomb/info-tech-canon` (Forgejo id 47)

This is the single recorded go-live moment the gate existed to create — not
"infrastructure is ready," but **a named Phase is authorized and declared**.

---

## 1. Pilot scope covered by the alpha/beta legal waiver

Per `SCOPE.md` §1, full specialist legal review of TRSL/CUA V1C1 is deferred
until the framework moves out of beta. T05 acceptance confirms that this
waiver covers the following **pilot scope** only:

| Dimension | Pilot scope |
| --- | --- |
| Licensor | Binky Hedgehog GmbH / Trust Service tenant `binky` (`specs/TRSL-Governance.md` §1) |
| First Phase | `trsl:phase:info-tech-canon-service-surface` on `coulomb/info-tech-canon` only |
| Legal text | TRSL V1C1 + CUA V1C1 as preliminary candidates under the existing alpha/beta working defaults (`history/260729-TRSL-Jurisdiction-Synthesis.md` §3, `history/260729-TREN-Synthesis.md`) — governing law/arbitration, liability cap, data protection, Enforcement Network fee mechanics as synthesized, not as counsel-finalized production terms |
| Commercial activity | Development Credit may be tracked for this Phase; Commercial Entitlements under this Phase may be granted only under the same alpha/beta risk acceptance |
| External contributions | **Still blocked** — CLA remains draft (`specs/TRSL-ContributorLicenseAgreement-Draft.md`); `CONTRIBUTING.md` external-contribution block remains in force until CLA is separately accepted |
| Other product lines | **Not** authorized by this T05 acceptance. `net-kingdom`, `railiance-vergabe-teilnahme`, and any further Phases each need an explicit follow-on declaration (same process; not a second T05 gate for the framework, but a deliberate Phase-by-Phase act) |

This is **not** a waiver of all risk forever, and **not** production legal
finality. It is a bounded pilot under known, already-documented alpha/beta
defaults.

---

## 2. Preconditions re-confirmed at acceptance

| Precondition | Status at go-live |
| --- | --- |
| WP-0004 / WP-0005 T10 syntheses | Done 2026-07-29 |
| Legal review waiver + pilot scope (this document §1) | Accepted 2026-08-05 |
| Licensor identity | Binky Hedgehog GmbH / `binky` |
| Hosted Trust Service software (WP-0006) | Done; pilot instance registered below |
| Draft survey + candidates (T02/T03) | Done; first live Phase is the former dry-run candidate |
| CLA | Draft only; external contribs remain blocked |
| Org-wide TRSL LICENSE text adoption | Already done 2026-07-30; `info-tech-canon` already carried TRSL V1C1 at go-live (no MIT-0 replacement step remained) |

---

## 3. Phase parameters (declared)

| Field | Value |
| --- | --- |
| `phase.id` | `trsl:phase:info-tech-canon-service-surface` |
| Milestone | `info-tech-canon-service-surface-v1 (ITC-WP-0001..0012)` |
| `source_revision` | `bd656d45165db3e49b971850d7d9487d41c76cc5` |
| Repo | `forgejo-coulomb` / id 47 / `coulomb/info-tech-canon` |
| Initial Target | **141,800 EUR** |
| Target Multiple | 100 (Product-defining) |
| Future License | MIT |
| Degeneration policy | `trsl:policy:linear-longstop-v0@1.0` |
| Longstop | 2029-01-01T00:00:00Z |
| Extension | `trsl:extension:development-license@1.0` |

**Initial Target caveat:** figure is the effort-calculator output from
`history/260730-EffortCalculator-CandidateApplication.md` §4, which
carries a sanity-check warning (12 finished workplans / 51 tasks vs ~1.42
raw days — likely under-count). Accepted for pilot as the transparent
calculator figure rather than a silent manual override; a versioned
correction remains available if pilot experience shows the target is
unworkable.

**Repo-local durable copy:** `info-tech-canon/trf/phase-service-surface.json`
(committed in that repo).

---

## 4. Trust Service registration (pilot instance)

Production reef deployment (`revenue.coulomb.social`, WP-0011) was **not**
ready at go-live. Registration used a dedicated **local pilot Trust
Service** instance so the Phase is live in a real Postgres-backed ledger
from day one, not merely a git file:

| Item | Value |
| --- | --- |
| Trust Service API (initial) | `http://127.0.0.1:8765` (local pilot; used only until public deploy) |
| Trust Service API (**POR, 2026-08-05 later same day**) | `https://revenue.coulomb.social` (railiance01; WP-0011 T05) |
| Control Plane | `https://revenue.coulomb.social/ui/` |
| Postgres (POR) | CNPG `target-revenue-pg` in namespace `target-revenue` |
| Licensor credential | `binky` / label `founding-admin` (token in `~/.config/target-revenue/revenue-coulomb-binky.token`, never committed) |
| Registration time (t0) on POR | 2026-08-05T15:55:52Z (public re-registration; local pilot ledger was empty) |
| Extension registered | `trsl:extension:development-license@1.0` |
| Ledger at registration | empty; Outstanding Target = 141,800 EUR |

Git-committed Manifest remains the durable declaration
(`specs/TrustServiceOnboarding.md` §1). Public Trust Service is the live
ledger authority after WP-0011 T05.

---

## 5. Explicitly not done by this go-live

- Selling Commercial Entitlements at scale or marketing TRSL as
  production-final legal text
- Accepting external contributions into the governed Milestone Release
- Declaring Phases for `net-kingdom`, `railiance-*`, or any other repo
- Deploying Trust Service / Control Plane to Railiance (`WP-0011`)
- Accepting the CLA draft

---

## 6. How to verify offline

```bash
# From target-revenue:
python scripts/trf_onboard.py validate ../info-tech-canon/trf/phase-service-surface.json
python scripts/trf_onboard.py status \
  --url http://127.0.0.1:8765 \
  --phase-id trsl:phase:info-tech-canon-service-surface
```