Aperture Bastion / Daylight / public review capsule
Public evidence for defensive machine-code research. Claims stay bounded to what the repository can regenerate.
Public preview · activation pending at last live readback
With a manually approved recipient record, the implemented browser client encrypts before upload and decrypts after ciphertext retrieval. The same-origin service accepts ciphertext and public metadata.
Activation status observed at . Point-in-time readback; not continuous availability.
In the reviewed client flow, messages are encrypted before upload. Private identities, passphrases, and decrypted bodies are not API fields.
Does not prove: uncompromised JavaScript delivery, browser integrity, or device integrity.
Recipients create identities locally and submit only a public record for manual owner review.
Does not prove: a keyname holder's real-world identity.
Accepted bottles receive public metadata, a ciphertext digest, retention timestamps, and a same-origin evidence URL.
Does not prove: the server was honest or never observed plaintext outside the implemented request path.
Aperture review surface
Aperture Bastion binds public artifacts to subject bytes, manifest references, and non-claim boundaries. The capsule gives reviewers handles to inspect; it does not promote local evidence into external authority.
The capsule digest is published with the release tag and commit reference.
Does not prove: production cryptography or runtime containment.
aperture-status.jsonThe public artifact profile rejects private-material patterns and unexpected files before publication.
Does not prove: host cleanliness or unknown-secret absence.
hosting-requirements.jsonClaim text is mapped to paths, commands, status values, and explicit non-claims.
Does not prove: certification, endorsement, or independent audit completion.
claim-evidence.jsonHosting requirements declare canonical HTTPS, redirects, status JSON, and required public assets.
Does not prove: current hosted compliance until the live gate passes.
hosting requirementsEvidence index
Each handle below answers what is shown, what local evidence checks it, and what it does not claim.
Maps public claims to local files, values, and validation commands.
Does not prove: external certification or government validation.
Open JSONPublishes release tag, capsule digest, hosted workflow, and artifact-diff status.
Runtime sandboxing is not proven. Host cleanliness is not proven.
Open statusRecords declaration refusal, fixture limits, external evidence gaps, and blockers.
Does not prove: Singularity declaration or independent audit.
Open statusProvides machine-readable research software metadata and citation information.
Does not prove: third-party indexing or endorsement.
CodeMetaDeclares canonical URL, header expectations, redirects, and public assets.
Does not prove: server compromise resistance.
Open requirementsSeparates evidence-bound claim verification from production security replacement claims.
Does not prove: endpoint protection, SIEM replacement, or IAM replacement.
Read boundaryDaylight proof ladder
Daylight distinguishes repository-owned progress from claim-usable external evidence. The v20 surface records a refusal, not a declaration.
Release evidence is local and reviewable through the Aperture status file and CI handles.
make daylight-v19-aperture-bastion-ci
Repo-owned ceiling progress is recorded, while fixture vectors and missing external evidence keep the declaration blocked.
make daylight-v20-aperture-singularity-ci
Review evidence, reproduce the lane, find a false claim, or show a reproducibility failure. Endorsement is not implied.
make site-validate
repo_owned_code_gap_count = 0 · repo_owned_ceiling_reached = truesingularity_possible_without_external_validation = false · declaration_allowed = falsev2.2.0-aperture-bastion · ce077fea615528634ad27fec516fdb402f101602 · 9109e7d9364f305a0618e6f5d810f3dd665d995e5c56f9d0ccc8d01875b9eec0 · aperture-bastion-public-v128564990503 · make daylight-public-artifact-firewall
Public technical review requested
The requested review actions are narrow: inspect the evidence map, reproduce the lane, identify false claim text, or show a reproducibility failure. No bounty, certification, or adoption claim is made here.
WuciOS 2.4.0 · Noether Forge
Noether Forge is the current Alpine-based realization of the
WuciOS Noether Core profile. Reviewers can inspect the build
source, pinned input lock, authenticated-fetch procedure,
schemas, tests, and bounded instructions at immutable commit
4783ebc.
No ISO, APK payload, package cache, compiled Wuci-Ji binary, kernel, initramfs, modloop, EFI image, firmware, or bootloader binary is distributed through this review lane. Reviewers fetch pinned Alpine 3.24.1 x86_64 inputs directly from upstream and build privately.
source-review-merged · source-only3.24.1 x86_64 · 52 locked APKsone clean checkout + host toolchainQEMU SeaBIOS + OVMF/UEFIThe earlier WuciOS v2.4 Reduction Gate and its Alpine substrate trial score remain design history; they are not a Noether Forge release score or binary-release authorization.
Artifact catalog
Catalog entries are public inspection material. They do not replace status JSON, commands, or claim boundaries.
Cross-surface review
Public trust is earned through the claim map, status files, commands, and reproducible repository evidence.
Gödel Boundary
Wuci-Ji and WuciOS v2.4 are not externally certified, not production authorized, not government approved, not a runtime sandbox claim, and not a quantum-safe claim from classical-only evidence.
This surface is not production cryptography, not a general runtime sandbox, not host-cleanliness proof, not whole-system post-quantum secure, not FIPS validation, not government validation, not external certification, and not independently audited.
NoEvidence(x) -> NoClaim(x)NoProof(x) -> NoRelease(x)ManualScore(x) -> Reject(x)