Skip to content

agent list JSON is now a sensing contract — stability guarantee needed #2

Description

@todie

The ecosystem integration program (cerebral-work/revenant docs/specs/ecosystem-integration-spec.md, ruling S4) makes herdr agent list the workstation session-sensing contract: revenant's second DiscoverSource impl is a herdr client, and agent_session.value (== the Claude Code transcript UUID) is the canonical workstation session identity adopted by reverie and cortex.

Ask: a documented stability guarantee on the agent list JSON shape in the unsigned distribution branch — fields never renamed/removed (additions fine), agent_session.value semantics frozen, and a fork-CI check that fails if the shape drifts (upstream merges from herdrdev/herdr are the risk vector: a vendor-branch rebase could silently change the schema that an audit system's sensing depends on — the exact silent-false-negative class the program just killed with the stale cortex binary, see reverie section §a).

Consumers at stake: revenant herdr sensing client (Wave A), reverie session-identity join, cortex fleet correlation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions