Skip to content

experiment: preserved ExecSurface typed-evidence initial trial - #161

Draft
hippoley wants to merge 2 commits into
mainfrom
experiment/execsurface-typed-evidence-initial
Draft

experiment: preserved ExecSurface typed-evidence initial trial#161
hippoley wants to merge 2 commits into
mainfrom
experiment/execsurface-typed-evidence-initial

Conversation

@hippoley

@hippoley hippoley commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Purpose

This PR exists only to trigger and preserve a zero-assistance external typed-evidence trial against the frozen ExecSurface packet.

It is not intended to merge.

Frozen evaluator-controlled inputs

  • CounterProof workload commit: 71b16b25d80d167d736ffd4ab7f6846980193811
  • ExecSurface packet: 03cb5dd656d6090cd2cc5c5d40885334b06b344a
  • ExecSurface experimental product target: cea214244d7efe05fea2108a5f5d8ed6287d9a3f
  • relationship: Unaffiliated
  • assistance before first result: ZERO_ASSISTANCE
  • workload origin: evaluator's own public project

Workload

The frozen CounterProof checkout runs:

python -m pytest -q
  tests/unit/test_conformance_receipt.py
  tests/unit/test_external_state_freshness.py

The trial harness preserves the first result even when build, doctor, observation, or consumer validation fails.

Raw typed evidence is stored only as a GitHub Actions artifact first so path privacy can be reviewed before any external submission.

Claims boundary

This PR does not claim ExecSurface validation, adoption, interoperability success, or fitness. PASS / FAIL / PARTIAL / UNSUPPORTED / NO_FIT are all acceptable initial evidence outcomes.

After the first result is preserved, the result may be submitted to AETHERXGLOBAL/execsurface using their external typed-evidence intake, with the initial outcome unchanged.

@hippoley
hippoley marked this pull request as draft October 7, 2026 10:07
@hippoley ChatGPT Codex Connector

hippoley commented Oct 7, 2026

Copy link
Copy Markdown
Owner Author

Initial zero-assistance result is preserved.

Run: https://github.com/hippoley/CounterProof/actions/runs/37605277588
Artifact: https://github.com/hippoley/CounterProof/actions/runs/37605277588/artifacts/11474407770
Artifact digest: sha256:cd18dd92a109f8a4108c23f7ed8d0c590b0067344846338a094bb4fe03afa5f9

Frozen evaluator inputs remained:

  • CounterProof workload: 71b16b25d80d167d736ffd4ab7f6846980193811
  • packet: 03cb5dd656d6090cd2cc5c5d40885334b06b344a
  • product target: cea214244d7efe05fea2108a5f5d8ed6287d9a3f
  • relationship: Unaffiliated
  • assistance before result: ZERO_ASSISTANCE

Preserved trial summary:

status: TRIAL_CAPTURE_COMPLETE_UNQUALIFIED
preflight: pass
build: pass
doctor: pass
observe: pass
consumer: pass
collection_health: complete
target exit_code: 0
typed_effect_count: 68
evidence_sha256: sha256:5f9d4a5447d3e258fb60ebc39fe7e23ef081e6a54179df034d9d58fa06f4f09f

Consumer result:

decision: EXPERIMENTAL_TYPED_EVIDENCE_V1_ACCEPTED_BOUNDED
implementation_version: 0.1.0-alpha.5
collection_health: complete
effect_count: 68
raw_event_count: 1189

Important first-run friction retained unchanged:

The trial guide says raw typed evidence may contain paths and should be inspected before sharing. Our workflow never cats typed-evidence.json; it only cats the privacy-minimized summary and consumer report.

However, during the harness's observe stage, the raw typed-evidence JSON was emitted to stdout and therefore entered the public GitHub Actions job log before the evaluator had any opportunity to inspect path sensitivity.

This does not invalidate the successful capture/consumer result. It is a separate privacy/evidence-handling finding about CI use of the external-trial harness.

No ExecSurface validation/adoption claim is made here.

This was referenced Oct 7, 2026
Open
Open
@hippoley ChatGPT Codex Connector

hippoley commented Oct 7, 2026

Copy link
Copy Markdown
Owner Author

External intake created from the preserved initial result:

AETHERXGLOBAL/execsurface#164

Status remains: external evidence submitted, qualification pending.

This draft PR should remain unmerged; it is the public preservation/driver record for the first zero-assistance attempt.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@hippoley