Skip to content

3a207ed3.md

Latest commit

 

History

History
185 lines (143 loc) · 14.7 KB

3a207ed3.md

File metadata and controls

185 lines (143 loc) · 14.7 KB
Raw
uid 3a207ed3
type project
status evergreen
state active
title Tropo Link
description The eighth subsystem hub. Houses the permanent Tropo agent + the linkage substrate between every Tropo Studio and Tropo HQ — agent identity (charter, soul, activation, boot extension), governance contract (kernel-managed-vs-user-owned), briefing package (release-news substrate), welcome playbook (four-phase first-user experience), harness-portable schedule registry + opt-in adapters, and the federation foundation thesis. The conduit. HQ pushes; Studios pull; nothing flows back.
owner tropo
created 2026-05-10
modified 2026-05-10
created_by argus-a55
modified_by argus-a55
tags
tropo-link
subsystem-hub
permanent-tropo-agent
hq-push-studio-pull
first-user-experience
harness-portable-scheduling
federation-foundation
v1.17.0
new-subsystem
p0
subsystem_name tropo-link
subsystem_scope Permanent Tropo agent (executive-class brand-as-agent host) + four-phase first-user experience (welcome.playbook successor to v1.4-era concierge paths) + kernel-managed-vs-user-owned governance contract + briefing-package release-news substrate + harness-portable schedule registry + Claude Code adapter (opt-in) + federation foundation thesis (v2.x+). The HQ↔Studio linkage as a coherent architectural piece.
file_ext md
schema_version 2
extraction_scope ship
slug tropo-link
lifecycle standing
last_release_reflected 1.17.0
aligned_with
8a4e21c5
governed_by 8a4e21c5
member_of
aae9a37b
8dd772a0
03ccd072
release_history
release_uid release_version summary registry_uid derived_from
4920ce3a
1.20.0
v1.20.0 ship — Tropo agent identity migration. Tropo's charter (9eaf53c6) + soul (14ed5da6) + agent-boot.extension (478b0b0c) migrated to vault/files/ with pre-existing UIDs honored. Permanent Tropo agent introduced at v1.17.0 now fully governed under v1.20.0 convergence pattern.
pending
capabilities_touched
release_uid release_version summary registry_uid derived_from
f6d7719f
1.19.0
v1.19.0 ship — welcome.playbook (e98420c3) migrated from playbooks/welcome.playbook.md to vault/files/<uid>.md with member_of edges declaring multi-subsystem reach (tropo-link primary + tropo-playbooks + tropo-agents + v1.17.0 activation root). how-tropo-update-orchestration-works (e668a385) migrated. The 8th subsystem (introduced at v1.17.0 with the permanent Tropo agent + tropo-link hub) carries the first-user experience surface; v1.19.0 ensures its primary playbook is governed alongside other Studio-level playbooks.
pending
capabilities_touched
release_uid release_version summary registry_uid derived_from
dbb0bace
1.17.0
Subsystem-introducing ship: NEW permanent Tropo agent + agents/tropo/ kernel-managed identity + CAPSULE.md governance contract + briefing-package release-news substrate + welcome.playbook four-phase first-user experience (3 v1.4-era concierge artifacts RECYCLED) + tropo-schedule.yaml registry + Claude Code adapter + Hooks 1+3 in agent-activation.playbook + Hook 2 in create-an-agent.playbook + v1.17.0 brief walk-locked v0.2 with multi-cycle Convergence Locks A-E + federation foundation thesis filed for v2.x+ + Tier 2 gap dogfood for v1.18.0+ + Studio Manifesto vocabulary dogfood for v1.18.0+. Soul principal-locked by Mike at ship; ship signal 'Lock and Ship.'
v1.17.0-tropo-link-row
capabilities_touched

Tropo Link — The HQ↔Studio Linkage Substrate

📍 Vault Path: tropo-subsystems → Tropo Link

🌳 Tropo-Nav Path (VS Code): ../../00-tropo-nav/00-tropo-active/tropo-work/dev-pipeline/v1.17.0 — First-User Experience Redesign + Permanent Tropo Agent/Tropo Link/3a207ed3 — Tropo Link.md

🌳 Tropo-Nav Path (chat): argo-os/00-tropo-nav/00-tropo-active/tropo-work/dev-pipeline/v1.17.0 — First-User Experience Redesign + Permanent Tropo Agent/Tropo Link/3a207ed3 — Tropo Link.md

🔗 This file — UID 3a207ed3 · type project · state active · status evergreen

↔ Siblings (71):

📥 Cited by (3):

Relations

Relation Target
Governed by subsystem-hub (8a4e21c5)
Aligned with subsystem-hub (8a4e21c5)
Member of tropo-subsystems (aae9a37b)
Member of Tropo Governance (8dd772a0)
Member of v1.17.0 — First-User Experience Redesign + Permanent Tropo Agent (03ccd072)

The eighth subsystem in the Tropo operating system. Houses the permanent Tropo agent + the substrate that makes the brand walk through the door in every user's Studio. HQ pushes; Studios pull; nothing flows back.

What this subsystem holds

This subsystem is the home of everything that makes Tropo (the brand-as-agent) work in user Studios:

The agent itself. A permanent executive-class agent named "Tropo" — the brand walking through the door. Not a persona; not a chat-assistant character; the OS the user installed, arriving as an agent in their Studio. Per-Studio lineage (T1, T2, ... T_n); kernel-managed identity (charter, soul, activation, agent-boot.extension); user-owned lived state (status, generation log, transfers, memory).

The first-user experience. A four-phase welcome flow (Phase 1 greet + first agent → Phase 2 optional learn-loop → Phase 3 shipped examples → Phase 4 real work in) authored as a Studio-level playbook. Replaces the v1.4-era concierge path concepts (welcome.playbook v0.6 + tour-tropo + personal-chief-of-staff, all RECYCLED at v1.17.0 ship).

The governance contract. Kernel-managed-vs-user-owned split declared in agents/tropo/CAPSULE.md. Identity ships from HQ; relationships stay with the user. The update pipeline reads the contract and behaves accordingly. Brand evolves; user-Tropo continuity persists.

The release-news substrate. briefing-package/00-index.md + briefing-package/current-release-notes.md template + lifecycle pattern (release-history/v<N>-notes.md archive on supersession). Each Tropo release ships news content via this substrate; Tropo's release-liaison role delivers via consistent pattern.

The harness-portable scheduling. L1 portable schedule registry (tropo-schedule.yaml) + opt-in harness adapters (Claude Code shipped at v1.17.0; other harnesses get adapters as needed; non-adapter harnesses use universal L1 boot-time check fallback).

The federation foundation. Future-cycle architectural thesis (Studio Registration + Studio-Prefixed UIDs at 7cac6473) for v2.x+ activation. Substrate for the marketplace + federation half of the strategic loop.

Architectural property: HQ push, Studio pull

At v1.17.0 ship, this subsystem is one-way by design. HQ pushes (releases, news, kernel-managed file refreshes). Studios pull on next boot or via update-detection trigger. Nothing flows back to HQ. Not generation counts. Not memory contents. Not what users are working on. Not how often Tropo runs.

This is a positive design property, not a temporary gap. It composes with:

  • Brand story — your Studio is yours; nothing leaves
  • Bounded-verification moat — the human is the verifier; HQ has no way to "see into" a Studio to validate it
  • Stranger-encounter expectations — the user downloaded a zip; the zip doesn't phone home

Eventual upward flow (marketplace publishing via explicit user action; federation sharing via explicit user action; opt-in crash reports) is always user-initiated and explicit — never telemetric, never automatic, never assumed. The federation foundation thesis at 7cac6473 is the substrate for those future moves; not v1.17.0 scope.

Member capabilities (v1.17.0 introductions)

UID Title Class
9eaf53c6 tropo-charter (vault/files/9eaf53c6.md) agent-charter (kernel-managed)
14ed5da6 tropo-soul (vault/files/14ed5da6.md) soul-letter (kernel-managed)
ad9256af tropo-activation (agents/tropo/tropo-activation.md) agent-activation (kernel-managed)
478b0b0c agent-boot.extension Tier 3 (vault/files/478b0b0c.md) agent-boot-extension (kernel-managed)
02c1958d agents/tropo/CAPSULE.md governance contract capsule (kernel-managed)
5f6b2cb7 briefing-package/00-index.md briefing-index (kernel-managed)
f6a967fd briefing-package/current-release-notes.md (v1.17.0 content) release-notes (kernel-managed)
e98420c3 vault/files/e98420c3.md playbook (kernel-managed via frontmatter)
98abee4e tropo-schedule.yaml registry schedule-registry (kernel-managed)
c0652d9c Claude Code harness adapter harness-adapter (kernel-managed)
9fc8a149 v1.17.0 design brief design-brief
03ccd072 v1.17.0 activation root project project
7cac6473 Federation foundation thesis (Studio Registration + Studio-Prefixed UIDs) note
154b0577 Tier 2 boot extension L1 entry gap (Self-Healing Path 2 dogfood) note

Note: file paths in agents/tropo/ are not vault/files/ entries at v1.17.0 ship; they're folder-shaped per Lock B exception. UIDs above are the conceptual UIDs each artifact carries in its own frontmatter; convergence Phase 2 (v1.20.0) migrates these to vault/files/<uid>.md entries in the canonical pattern.

Multi-cycle architectural commitments (Locks A-E inherited)

The v1.17.0 walk produced multi-cycle architectural locks that shape v1.18.0+ chain. This subsystem hub composes with all five (per v1.17.0 brief §12 (9fc8a149)):

  • Lock A — Universal Storage Convergence is the destination. This subsystem's artifacts migrate to vault/files/<uid>.md over v1.19.0 (Phase 1 — behavior primitives) + v1.20.0 (Phase 2 — agent identity). Substrate-form converges; this hub remains the canonical surface.
  • Lock B — Five exception classes. agents/tropo/ is the entry-point folder-shape exception. Thin-loader pattern preserves boot reliability; identity content migrates to vault/files/.
  • Lock C — Governance backstop hybrid (pedagogy-first; mechanical enforcement as safety net). This subsystem's CAPSULE.md is an early example of pedagogy-first capsule body — leads with WHY the contract exists, not just yaml schema.
  • Lock D — AGENTS.md retires for converged classes. This subsystem's agents/tropo/ AGENTS.md (none today) would only exist if folder-shape persists; convergence Phase 2 retires the need.
  • Lock E (sequencing). v1.17.0 (this cycle) → v1.18.0 → v1.19.0 (Phase 1) → v1.20.0 (Phase 2) → v1.21.0 (sa.* harden) → v1.22.0 (Vault Import + Export) → v1.23.0 (Memory) → v2.0.

Composes with (other subsystem hubs)

  • Tropo Agents (99ed55fd) — Tropo is an agent-class member; this hub is meta-level (Tropo + its supporting infrastructure as a coherent piece) while Tropo Agents is broader (every agent in the Studio). The two compose; some Tropo artifacts are dual-member.
  • Tropo Playbooks (76bab75f) — welcome.playbook is dual-member (this hub + Tropo Playbooks subsystem).
  • Tropo Governance (8dd772a0) — CAPSULE.md governance contract + the Self-Healing Primitive Tropo internalizes are governance-class; dual-member.
  • Tropo Library (1aba710c) — voice substrate (Studio Manifesto + canonical Tropo Work narrative) lives in tropo-library; tropo-link references but doesn't duplicate.
  • Tropo Documentation (f87e33f0) — release-notes content authored each release composes with documentation-class artifacts.

Future-cycle evolution

Per Lock E sequencing:

  • v1.18.0 (Capsule Library Phase 1) — capsule-body-as-pedagogy refactor; this hub's capsule-typed artifacts may benefit from refresh
  • v1.19.0 (Convergence Phase 1) — behavior primitives (welcome.playbook, schedule registry, Claude Code adapter) migrate to vault/files/<uid>.md with type: playbook / type: schedule-registry / type: harness-adapter
  • v1.20.0 (Convergence Phase 2) — agent identity (charter, soul, activation, agent-boot.extension) migrate to vault/files/<uid>.md with thin-loader pattern at agents/tropo/ for invocation
  • v1.22.0 (Vault Import + Export) — Phase 4 of welcome.playbook gets automated tooling; first concrete encounter with UID collision case → defers to federation foundation thesis
  • v1.23.0 (Memory System Eval + Refinement) — revisits Q9 memory-update step (Path 1/Path 2 hybrid) with real signal from v1.18.0+ release-cycle data
  • v2.0 (User-readiness ship) — doors open; this subsystem is the load-bearing first-user encounter substrate

Tropo Link Subsystem Hub | UID 3a207ed3 | v1.17.0 cycle Stream G | Argus A55 | 2026-05-10 "The brand walks through the door. The agent is permanent. The Studio operates under a host who doesn't leave." "HQ pushes; Studios pull; nothing flows back."