Skip to content
tcp.systems docs

Wayfinder: tcp.systems harness

Destination

Section titled “Destination”

A DSH-native operating harness for tcp.systems: it observes company state, runs deterministic gates, computes the decision frontier, runs evals, and keeps agents grounded — so research, planning, buildout and implementation proceed with human involvement only at genuine decisions.

Notes

Section titled “Notes”
  • Repo: tcpsystems/ops. Company: tcp.systems (AI/ML). Products: acumen (router), massprox (supply).
  • Reference only: the Foxcore ops harness (../../foxcore-cloud/ops). Do not import its state or gates.
  • Roles: cartographer, orchestrator, developer, maintainer, reviewer, researcher, evaluator (agents/roster.json).
  • Skills: skills/registry.json maps each role to the skills it should load. The harness never vendors credentials.
  • Rule: a gate verdict is evidence about a tree, not proof a feature works. Quote status.json timestamps.

Decisions so far

Section titled “Decisions so far”
  • Harness shape: a standalone Node harness with a deterministic gate, a health observer and a decision frontier — independent of any product repo.
  • Evidence model: observed/derived/unknown claim labels enforced by review, with address-level citation checks and no truth claims from a green gate.
  • Product gates: one command runs every active project’s declared gate with a per-product timeout and records the real exit code; exit 0 all pass, 1 fail/timeout, 3 cannot certify, and an unavailable product is never green.
  • Secrets and dependencies: a dependency-free credential-shape scan with a reasoned allowlist and no matched values in logs; zero runtime dependencies enforced, with OSV advisory lookup kept as a separate non-gating report.
  • Memory capture: local JSONL events for gate verdicts, decisions and incidents; explicit consent policy, 1–365 day retention, redaction before write, no external telemetry, and capture refused without consent.
  • Console access: loopback through the authenticated DSH web route, tailnet only by binding, no public hostname without Lead approval; the console shows declared status only and the check enforces noindex, CSP, no script, no external assets and no host paths.
  • DSH surface: a read-only tcp_harness model tool plus the tcp.systems sidebar tab, delivered by the plugin; it exposes declared status only and never secrets, environment, product internals or host paths.
  • Plugin packaging: the Creator-Mode bundle @local/dsh-tcp-harness installs from this repo, registers Host routes, the tool and the sidebar tab, writes no global state and is verified on a temporary DSH instance.

Not yet specified

Section titled “Not yet specified”
  • None: all six increments are decided and implemented. New fog enters through a new wayfinder ticket.

Out of scope

Section titled “Out of scope”
  • Product implementation for acumen, massprox, radar, iptvcatalog or dock: each product repo owns its own code and gate. This harness only observes and coordinates.