Self-hosting MVP: services on users' computers, verified by agreement, credited in TRI (off-chain first), everything decided in .t27 #1756

The owner, 2026-10-10 (translated):

• move everything into one repository and one service managed through .t27, based on trios;
• ideally, an app that runs services on other people's computers instead of a hosting provider. That is decentralized hosting on users' machines, paid in TRI for proof of work / proof of compute, so we stop paying for the hosting of the services we need;
• build an MVP of self-hosting.

What already exists (read before building)

• Pull-based remote executors. trios-bee-runner-1/2 already pull work from the Queen, hold leases and report back. That is most of a host agent.
• A leased link between nodes. specs/queen/netlink.t27, fix(queen): PgLink made safe before its first caller - node incarnations, a fenced lease on its own thread, mail acknowledged after it is handled (Closes #1714) #1724, has node incarnations, 20 s leases with 5 s beats, and fencing. The actor runtime already runs across nodes on it.
• A remote job runner. t27c bench-agent (t27#8153) runs silicon jobs on a machine next to a board, after an approval comment.
• Proof by agreement. Signed corpus receipts and the three-way decision replay (t27#8317) already decide "did two runs produce the same result".
• The proof format. gHashTag/tri-net's DePIN Compute arm defines the proof payload (model_hash, input_hash, output_hash, ops), settled through MiningPool.claimReward().
• TRI as it stands, from gHashTag/golden-chain-international FACTS.md §6, verbatim facts:
  • TriToken lives on Base Sepolia (testnet only). 100% of the supply is locked in MiningPool, and the ownership of both contracts is renounced.
  • A token leaves the pool only as a reward for a verified compute proof from a registered chip, on a 4-year halving curve.
  • Any promise of token income for hardware or compute, any sale or listing, needs legal review first.

Hard constraints, so the MVP is honest

1. A stranger's computer can read everything a service it runs holds. Secrets (API keys, DB URLs) and client data (CRM, Telegram messages) therefore never go to a host outside the owner's trust. Three trust tiers:

   • owner (the owner's own machines): any workload;
   • trusted (named people): stateless services, with secrets scoped to that service;
   • public (anyone): only deterministic, secret-free, PII-free jobs, whose result is checked by agreement with another host.

2. Proof of compute is solved only for deterministic jobs. k-of-n hosts run the same pinned job, the hashes of their outputs must agree, and only agreeing hosts earn credit. Long-running services get uptime proved by challenge probes; that cannot prove the work was correct, so services stay in the owner and trusted tiers.

3. TRI accrues off-chain in the MVP. The credit ledger is keyed by host key. On-chain settlement needs both a host identity the pool accepts (today the pool requires a registered chip) and the legal review FACTS.md requires. The MVP pays nothing on-chain and claims no token value.

4. Only t27. Every decision is a .t27 spec with tests, compiled to a card:

   • host eligibility per tier;
   • placement and failover;
   • lease expiry;
   • quorum and agreement;
   • credit per verified unit;
   • the settlement threshold.

   TypeScript is glue: HTTP, process control, storage.

MVP (slice 1)

• Specs (specs/hosting/*.t27):
  • host.t27: tiers, capacity, lease, and eligibility per workload class;
  • placement.t27: fit, spread, k replicas, and moving work when a lease lapses;
  • proof.t27: the receipt shape aligned with tri-net's Compute arm, the k-of-n agreement, and the verdicts;
  • credit.t27: TRI units per verified job, the off-chain ledger rules, and the settlement threshold.
• Queen endpoints in trios, behind TRIOS_HOSTING=on:
  • register a host (it holds an ed25519 key);
  • beat;
  • lease a job;
  • post a signed receipt;
  • read the public ledger.
• Host agent trios host, which a user runs:
  1. generates a key;
  2. registers and beats;
  3. pulls a job: a pinned OCI image digest, or t27c test-report on a spec at a commit, run sandboxed with no secrets;
  4. posts the output hash and a signed receipt.
• Demo: two hosts, the owner's Mac and one other machine or process, run the same job. The Queen sees the hashes agree and credits both. A third host that tampers with the output gets no credit.

Slice 2

• A stateless service hosted on an owner-tier or trusted-tier machine, reached through a reverse tunnel to the Queen. Candidates: the STT pods gigaam and parakeet, or a static site.
• A topology .t27 that describes every service. It is the same spec the disaster-recovery template needs (Disaster recovery: back up all data off Railway and GitHub, and a template that redeploys the whole project on a new account t27#8675).

The consolidation into one repo is planned separately, because trios is public and some service code (999-multibots-telegraf) is private.