Repository navigation
ExecSurface v1.0.0 — Independent External Evaluation & Post-Release Review #118
Description
ExecSurface v1.0.0 — Independent External Evaluation & Post-Release Review
Current evaluation target
ExecSurface v1.0.0 is the current published stable release within the documented Linux x86_64 + native ptrace boundary.
- Release:
v1.0.0 - Release source:
e70169b959f2163715090c371335fa6c5591e3e4 - Stable GitHub Action:
AETHERXGLOBAL/execsurface@v1 - Immutable Action pin:
AETHERXGLOBAL/execsurface@v1.0.0 - Registry package:
execsurface = 1.0.0 - P8 evidence authority: P8 — External Validation, Independent Reproduction & Architecture Criticism #114
- External real-workload evidence: Post-v1 — External real-workload evidence (historical P9.5) #140
- Current status authority:
docs/STATUS.md - Technical evaluation path:
docs/TECHNICAL_EVALUATION.md
Independent external validation is not claimed. Stable-v1 internal qualification, public release success, downloads, stars, forks, outreach and AETHER X-controlled tests are not substitutes for independent external evidence.
Install and evaluate v1.0.0
crates.io
cargo install execsurface --version "=1.0.0" --locked
execsurface --version
execsurface doctorGitHub Action
Moving stable channel:
uses: AETHERXGLOBAL/execsurface@v1Immutable evaluation pin:
uses: AETHERXGLOBAL/execsurface@v1.0.0What counts as useful external evidence
Positive results are not required. Useful evidence includes:
- zero-assistance installation/reproduction success or failure;
- real external workload results;
- false PASS / false REVIEW / false incompleteness;
- unsupported-environment findings;
- architecture criticism or counterexamples;
- portability, performance, privilege, privacy or setup friction;
- interoperability or redundancy/no-fit findings.
Please preserve the initial result before AETHER X troubleshooting changes the attempt.
Where shareable, report:
- OS, kernel, architecture, VM/container/CI context;
- exact ExecSurface version/install route;
- target command/workload;
doctoroutput/state;- PASS / REVIEW / BLOCK / ERROR and exit code;
- completeness/observer-health state;
- machine-readable evidence needed to reproduce the finding;
- suspected false classifications or semantic ambiguity.
Do not post credentials, private source, environment secrets, stdin, file contents or network payloads.
Product boundary
ExecSurface is a runtime behavioral verification / execution-semantics / semantic-evidence correctness product.
It is not classified as a cybersecurity product or cybersecurity research project. It is also not antivirus, EDR, SIEM, malware detection, a sandbox, or proof that software is safe.
observed behavior != all possible behavior
Evidence qualification
Returned evidence is qualified separately under #114. A report can be valuable while still being PARTIAL, FAIL, NO_FIT, UNSUPPORTED or otherwise non-validating.
External organization names, maintainer replies, stars, forks, reactions, routing guidance and positive discussion must not be converted into endorsement/adoption language without exact supporting evidence.
Historical Alpha.5 baseline
This issue originally opened as the public post-release review hub for v0.1.0-alpha.5.
Historical Alpha.5 identity is retained for provenance:
- release:
v0.1.0-alpha.5 - release source:
9e73b925d55557e33de1b0813995609aaefdc037 - frozen qualification source:
5067200452c174da6bc8d9d7ecf6957ee379f0a2
Alpha.5 remains immutable historical evidence. New general external evaluations should target stable v1.0.0 unless a protocol explicitly freezes an older source for a specific historical experiment.
Activity
[-]ExecSurface Alpha.5 — Independent External Validation Request (P8 Release Gate)[/-][+]ExecSurface Alpha.5 — Independent External Validation & Post-Release Review[/+]aetherxeg-source commentedon Oct 1, 2026
Post-release verification & repository operations update — 2026-10-01
ExecSurface Alpha.5 remains publicly released as
v0.1.0-alpha.5.Public-release state
v0.1promotion only after public proofs, crates.io publication, and zero-contact registry installation.Repository operational cleanup
The repository has now been reorganized so the active engineering surface reflects the current product instead of exposing completed research and one-shot milestone automation as if it were ongoing operations.
.github/workflows/now contains the durable operational CI/release/evaluation workflows only..github/workflow-archive/pre-operational-cleanup-2026-10-01/.action/release-tag.txtinstead of hard-coding a historical alpha.docs/README.mdnow provides a documentation/source-of-truth map separating current public guidance from historical engineering evidence.ROADMAP.mdnow describes the forward post-Alpha.5 program; the complete pre-Alpha.5 roadmap is preserved unchanged atdocs/archive/ROADMAP_PRE_ALPHA5.md.main.Post-cleanup verification
Current
mainis08901b9a735e1c7fd9e11a03bb10e9f1805f2569.On that exact HEAD:
36917368208: PASS.36917368117: PASS.Earlier cleanup-stage CI, public-consumer and adversarial-regression runs also passed; no acceptance rule or adversarial threshold was weakened as part of the cleanup.
This update records release/operational state only. It is not an external-validation claim. Independent reproduction, criticism, counterexamples, interoperability findings and real-workload reports remain welcome against the published Alpha.5 release.
aetherxeg-source commentedon Oct 1, 2026
Contributor entry points
If you want to contribute code/docs rather than only report an evaluation result, these newcomer-scoped tasks are now open:
hello-driftPASS → REVIEW exampleAll are intentionally scoped to preserve the current evidence boundaries. A contribution, successful example, or self-test is valuable engineering work, but it is not automatically independent external validation. Negative findings discovered while working on any task should be preserved and linked back here.
aetherxeg-source commentedon Oct 3, 2026
Current production-readiness evidence gap
The repository now has genuine external contributions (#126, #127, #128), and they are recorded without being inflated into independent validation.
For the next external-evidence step, issue #140 now tracks external real-workload production evidence under the existing P8-A4 protocol.
Useful evidence is not required to be positive. If you independently use Alpha.5 on a workload/project you control or choose (not an AETHER X-authored demo), reports of useful fit, noise, setup friction, unsupported environments, false REVIEW, suspected false PASS/incompleteness, privacy concerns, operational cost or no-fit are all useful.
Please preserve the initial result before any AETHER X troubleshooting and include the workload/command, version/install route, Linux environment, baseline-approval path, verdict/error/completeness state and reproducible logs where shareable. Do not post secrets or private source.
This request does not claim that current contributors, reviewers, or organizations validate or adopt ExecSurface. P8 remains open until the preregistered current execution/use + challenge/interoperability evidence minimum is genuinely satisfied.
aetherxeg-source commentedon Oct 8, 2026
2026-10-08 status transition: this public evaluation hub is being retargeted from the historical Alpha.5 release to the current stable
v1.0.0release. Alpha.5 identity and provenance remain explicitly retained; the change does not relabel any prior result as v1 evidence or independent validation.[-]ExecSurface Alpha.5 — Independent External Validation & Post-Release Review[/-][+]ExecSurface v1.0.0 — Independent External Evaluation & Post-Release Review[/+]