Skip to content

Implement ADR-035 terminal boundary transitions and system-action transcript #17

@mdheller

Description

@mdheller

Scope

Implement TurtleTerm consumption of the merged SocioProphet/prophet-platform ADR-035 transparent fault attribution contracts.

Canonical upstream dependency:

  • SocioProphet/prophet-platform squash commit 86b0fbc203b595fb7ef103ee06f845211ea46378
  • ADR: adr/ADR-035-transparent-fault-attribution-and-embedded-engine-policy.md
  • Contracts: FaultEnvelope, EngineManifest, BoundaryTransition, RolloutReceipt, DiagnosticRedactionPolicy

Design intent

TurtleTerm must separate the human terminal transcript from the system/agent/helper action transcript. Shell execution, PTY lifecycle, SSH/cloud sessions, preview engines, automation bridges, environment realization, mounts, and policy denials must become attributable events.

Acceptance criteria

  • Add TurtleTerm EngineManifest examples for terminal bridge, PTY/session bridge, shell command wrapper, agent gateway, tmux bridge, web/cloud session, preview pane, diagnostic reporter, and automation bridge.
  • Add BoundaryTransition fixtures or emission stubs for shell execution, PTY spawn, SSH/cloud session start, automation bridge use, mount/file access, network open, policy gate, and diagnostic export.
  • Add FaultEnvelope fixture for shell wrapper failure, PTY failure, and automation bridge denial.
  • Add a system-action transcript design doc that remains separate from the human-visible terminal transcript.
  • Transcript entries must link back to user intent or agent intent receipts when available.
  • Diagnostic export must use DiagnosticRedactionPolicy tiers.

Non-goals

Do not make the human terminal transcript noisy. The system-action transcript is a separate evidence lane and should be inspectable/exportable without polluting normal operator workflow.

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