Daylight v15 Meridian evidence-derived sovereign mathematics banner

Daylight v15 Meridian evidence surface

No Such Machine

A public home for defensive machine-code research, sealed artifacts, receipt-bound release, and the evidence that keeps Wuci claims narrow enough to verify.

View source Read boundary

Research artifact Not production cryptography or independent audit status.

Evidence first Proof lanes are local, deterministic, and reviewable.

Bounded claims No runtime sandbox or quantum-safe claim is made here.

System shape

A small machine for claims that can be checked.

Wuci-Ji composes WJSEAL artifacts, authorization receipts, Gate checks, witness bundles, ledger history, signed local installation evidence, and Daylight protocol-state evidence into an inspectable research system.

sealed artifact
authorization receipt
Gate contract check
controlled release
public witness bundle
ledger history

Challenge issued 2026-06-30

Public falsification lane is open.

No Such Machine has issued a public challenge to @780thC and any other reviewer: inspect Daylight v15 Meridian logic, reproduce the proof lanes, and falsify any claim that does not survive the evidence. The target is the published research surface, not a network, system, or third-party asset.

Open Daylight v15 Read scorecard

Review surface Ready to inspect

Source, schemas, examples, scorecards, boundary docs, and the Daylight v15 Meridian CLI are published in the repository.

Local proof lane Ready to reproduce

make daylight-meridian-frontier reports a 998,900M internal ceiling with 1,100M of external residue.

Repo 1000 claim gate Blocked by design

Daylight_v0.6 remains 975/1000 with ready: false. External review-set evidence and integrated Daylight authority evidence are still required.

Rules of engagement Defensive only

The accepted lane is public evidence review, reproducible command output, and independent attestation. No exploit harness or network attack lane is part of this challenge.

Meridian browser envelope

Encrypt locally when the evidence gate permits it.

This browser lane never uploads your file. It creates a local Meridian Browser Envelope with Web Crypto, binds the ciphertext to the v15 evidence ceiling, and gives you a separate private download key. Policies above the current internal evidence state are refused.

NoEvidence(x) -> NoSeal(x)
NoProof(x) -> NoOpen(x)
ManualScore(x) -> Reject(x)

The Meridian browser envelope runs entirely in JavaScript with Web Crypto. Enable JavaScript to seal or open files locally; nothing is ever uploaded.

File Policy score floor

Required closed obligations Master law executable Fail-closed tests Crypto KAT vectors External falsification program

I understand this is a browser research profile, not production cryptography or external certification.

Waiting for a file and an admissible policy.

Meridian Authorized Envelope

Seal by evidence. Open by proof.

The MAE plate is the visual map for the v15 envelope lane: evidence derives the scorecard, policy binds into the authorization tag, and open remains bottom unless the caller re-derives a verifying state.

Read the envelope design

WUCI v15 MAE Meridian Authorized Envelope visual map — WUCI v15 MAE: evidence-bound cryptographic gate, 30 June 2026.

Evidence lanes

Proof surfaces with explicit refusal lines.

Envelope

Assembly-owned WJSEAL artifact sealing and opening paths.

Boundary: not a general secret-management platform.

Gate + Warrant

Contract checks and deterministic fixture quorum receipts.

Boundary: fixture authority only.

Witness + Ledger

Public evidence bundles and local deterministic hash history.

Boundary: not an operated public log service.

CAGE + QCAGE

Artifact legitimacy checks and quantum-risk metadata.

Boundary: not OS containment or PQ security.

INSTALL

Signed local install manifest checks and copied root-key proof.

Boundary: no remote-code shell pipeline.

Daylight v15 Meridian

Evidence-derived scoring, obligation closure, and refusal of manual scores.

Boundary: research artifact, not external certification.

Wuci-OS image lane

An evidence-first operating-system image surface.

Wuci-OS verifies an operator-supplied musl ISO, records digest evidence, checks live layout, emits QEMU boot plans, and presents a Wuci-native live profile with the WJ prompt identity.

Live command: INSTALL starts the automated Wuci install path.
Default account: wj is the live/demo admin login and prompt identity.
Release stance: Current OS work remains local image evidence and boot planning.

Command deck

Focused lanes for build, proof, and preview.

Wuci-OS regression

make wuci-os-test

Final ISO lane

tools/wuci-os final-iso --force --remaster-rootfs --install-suite-packages

NOXFRAME console

tools/wuci-noxframe --console --yes

Visual evidence

Actual artifacts from the Wuci-OS documentation set.

WUCI v15 MAE Meridian Authorized Envelope sheet — WUCI v15 MAE envelope

Daylight v15 Meridian evidence sheet — Daylight v15 Meridian

Daylight and Wuci wire model — Daylight/Wuci wire model

Boundary

Blunt by design.

Wuci-Ji is not production cryptography, not a general runtime sandbox, not post-quantum secure, not production authority, and not independently audited. A boundary is only treated as enforced when the repository has implementation and tests for that behavior.

Open the full security boundary