Skip to content

Add model-free configured DING activity matrix - #59

Draft
myobie wants to merge 5 commits into
mainfrom
issue-57-ding-activity-skeleton
Draft

Add model-free configured DING activity matrix#59
myobie wants to merge 5 commits into
mainfrom
issue-57-ding-activity-skeleton

Conversation

@myobie

@myobie myobie commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Related to #57.

What changed

  • retains the exact-source PTY activity-lease, guarded-send, aggressive-control, and PTY-boundary A/B cells
  • adds an integrated generated-sidecar A/B against corrected st2 PR #123 exact head d7500b0fcad8bb268da9da96c0226d9caddbe305 and accepted release binary SHA256 705ad3ebd0bce497a4117c7c7993505c0579fc1f7df2421e0525a22208f6949f
  • proves configured generic adapter argv expansion from the final managed task environment, with exact argument boundaries and no shell
  • exercises fresh idle guarded writes, exact hook-owned control ingress, DND/stale/error holds, typed receipts, a real sidecar/task restart, and a three-message FIFO burst
  • updates the adapter evidence ledger, harness exclusions, generated catalog, README, and Agent Spec

Result

Across nine matched scenarios and 11 durable messages, both arms preserve identical bodies, SHA256 values, FIFO order, and exactly-once archive delivery. In both the PTY-boundary and integrated receipts, the generated unconfigured arm makes 6 unsafe PTY writes while activity is non-idle, stale, or unknown; the guarded/configured arm makes 0.

Collision evidence is intentionally narrower in both cells. In the active-turn case, each matrix first observes the partial draft as the live PTY suffix, then directly observes A's DING bytes appended after it. B leaves the draft untouched: 1 directly observed partial-draft collision versus 0. The other 5 unsafe A writes are not claimed as observed collisions.

In the integrated cell, B performs 5 exact guarded idle writes and routes 6 non-idle messages through durable hook ownership. The corrected configured sidecar launches twice through the real generated task environment (initial boot and crash/restart), never selects fallback, and leaves zero of 8 tracked process identities and zero PTY sessions alive. modelCalls is exactly 0.

Exact dependencies

  • st2 PR #123: d7500b0fcad8bb268da9da96c0226d9caddbe305; release binary SHA256 705ad3ebd0bce497a4117c7c7993505c0579fc1f7df2421e0525a22208f6949f
  • PTY activity base: 46c71d31c0d6daee43adf568061b2b84a65ae8c0
  • PTY guarded successor: 743ceb796a41a3282e31382575bff0d0e3826d59
  • complete corpus runner: st2 c6846f6239329f0803142afc06c15a07b93937c1; binary SHA256 2bba8d58be24250bc262f75f835ce2d780369add275774f3f2135c623d23d29c

Validation

  • ding-delivery-pty-ab: 9/9
  • ding-delivery-st2-rich-ab: 11/11
  • ding-adapter-fixture-contract: 8/8
  • complete 51-cell model-free corpus preflight: PASS
  • git diff --check: PASS

Limits

This is integrated configured-st2 evidence with a synthetic generic activity adapter and deterministic hook consumer. It is not real-provider acceptance: immutable Codex and Claude activity/hook fixtures, owner review, separately authorized live-pane execution, merged dependencies, and release artifacts remain outstanding.

No paid or provider call was authorized or made. This PR remains draft; do not merge or deploy from this evidence.

@myobie myobie changed the title Add model-free DING activity and guarded-send matrix Add model-free configured DING activity matrix Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant