Skip to content

5f6b2cb7.md

Latest commit

 

History

History
87 lines (64 loc) · 4.63 KB

5f6b2cb7.md

File metadata and controls

87 lines (64 loc) · 4.63 KB
Raw
uid 5f6b2cb7
type briefing-index
agent tropo
title Tropo — Briefing Package Index
description Entry point for the Tropo agent's briefing package. Read at Group 2 of agent-activation.playbook when no living-transfer exists (T1 first-generation in this Studio) OR as supplementary boot context. Points at current-release-notes.md (latest release news) + supporting briefing artifacts.
version 1.0
for_successor T1+ (every Tropo generation in this Studio)
read_order secondary
created 2026-05-10
created_by argus-a55
modified 2026-05-10
modified_by argus-a55
schema_version 2
extraction_scope ship
governance_class kernel-managed
governed_by 222873b9
member_of
99ed55fd
8dd772a0
03ccd072
tags
tropo-briefing-index
kernel-managed
v1.17.0
refreshed-each-release

Tropo — Briefing Package Index

Entry point for the Tropo agent's briefing package. Read at Group 2 of agent-activation.playbook when the living-transfer is absent (T1 first-generation) OR as supplementary boot context.

What's in this briefing package

The briefing package is kernel-managed (refreshed by the update pipeline on each Tropo release). It carries:

Artifact Purpose Refresh cadence
00-index.md (this file) Entry point + map of the briefing package Each release
current-release-notes.md Latest Tropo release news (what's new in the current version) Each release; previous version archived to release-history/
release-history/<version>-notes.md Superseded release notes preserved as historical record Append on each release (previous current-release-notes.md moves here)

What's NOT in this briefing package (lives elsewhere):

  • Identity (tropo-charter.md, tropo-soul.md, tropo-activation.md, agent-boot.extension.md) — agents/tropo/ root; loaded directly at boot per agent-activation.playbook Group 2
  • Lived state (tropo-status.md, tropo-generation-log.md, transfers/, .tropo-capsule/memory/) — user-owned; lives across releases per agents/tropo/CAPSULE.md governance contract

How this briefing package is used

At Tropo boot (T1 first-generation in this Studio):

  • agents/tropo/transfers/living-transfer.md is absent (no predecessor Tropo to inherit from)
  • agent-activation.playbook Step 2.4 fallback chain reads this briefing package
  • Read current-release-notes.md to know what's current; proceed to startup signal per invocation pattern

At Tropo boot (T2+ returning generation):

  • Living-transfer is the primary briefing source
  • This package is supplementary — current-release-notes.md checked for any release news the prior generation didn't already deliver (compare last_delivered_version field)

At Tropo update (kernel-managed file refresh detected):

  • This whole package refreshes from the new release
  • current-release-notes.md carries the new release's news content
  • Tropo's update-orchestrator role surfaces the news at next Pattern 1 returning startup signal OR Pattern 3 scheduled summary

Release-history pattern

When a new Tropo release lands and current-release-notes.md refreshes, the previous version's content is preserved at release-history/v<previous>-notes.md. That keeps:

  • Historical record of what each release introduced
  • Reference for users who want to look back at past release news
  • Substrate for "show me what changed across the last N releases" queries

The release-history/ folder is empty at v1.17.0 ship (Tropo is new; no prior release history exists). On v1.18.0 ship, v1.17.0's current-release-notes.md content moves to release-history/v1.17.0-notes.md; new v1.18.0 content lands as the new current-release-notes.md.

Composes with

Tropo Briefing Package Index | UID 5f6b2cb7 | v1.0 | v1.17.0 cycle Stream C | Argus A55 | 2026-05-10