README.md
OSL and Neuralese
README.md
1 # OSL-Core 0.5 Semantic Independence v0.1.0
2
3 OSL-Core 0.5 extends the Core 0.4 receipt-hardened runtime with separately
4 implemented semantic verifiers for the finite numerical, contract, session,
5 metadata-facing, and audit-intrinsic fragments. These verifiers operate on
6 supplied source, receipts, and final state without importing or invoking
7 `OSLRuntime`. Same-runtime replay remains supplementary and is not counted as
8 independent semantic evidence.
9
10 This is a separate executable development release. It does not rewrite the
11 frozen Operator Symbolic AI Language v0.5 / OSL-Core 0.3 package or relabel
12 Core 0.4 evidence.
13
14 ## What changed
15
16 - added independent reconstruction of spaces, vectors, operators,
17 applications, transport, and finite projector/intertwiner checks;
18 - added independent reconstruction of all five implemented temporal-contract
19 templates and feedback-deadline obligations;
20 - added independent finite-session declaration, graph-verification, start,
21 advancement, history, terminal, and per-domain rollback checks;
22 - added reconstruction of secret commitments, metadata values, assertion
23 accounting, `show` bindings, and their per-domain rollback behavior;
24 - added independent recomputation of reports embedded by `verify_receipts`;
25 - added a fail-closed aggregate semantic report that keeps component results
26 separate;
27 - rejected unknown operator kinds, duplicate transport results, duplicate
28 secret or metadata names, invalid inference confidence, nonfinite numerical
29 input, dimension-incompatible projectors, and invalid check tolerances;
30 - retained the versioned `osl.core.receipt.v2` lifecycle while changing the
31 receipt `core_version` to `0.5`.
32
33 ## Verified release facts
34
35 | Gate | Result |
36 |---|---:|
37 | Packaged source corpus | 66/66 |
38 | Accepted / expected rejection | 42 / 24 |
39 | Native Core 0.5 receipts | 1,825 |
40 | Independent semantic aggregate | 66/66 |
41 | Full test suite | 168/168 |
42 | Focused Core 0.5 suite | 75/75 |
43 | Discovery Bridge | 3/3 programs, 71 receipts |
44
45 The focused suite contains positive reconstruction, malformed-input,
46 fully-rehashed semantic-mutation, rollback, integration, and language-hardening
47 cases. It is a fixed finite gate, not exhaustive adversarial testing.
48
49 ## Independent coverage
50
51 The aggregate in `reference/osl_semantic_kernel.py` combines five bounded
52 components:
53
54 | Component | Independently reconstructed surface |
55 |---|---|
56 | Numeric | Spaces, vectors, operators, application, transport, projector and intertwiner checks |
57 | Contracts | Five templates, feedback deadlines, explicit checks, finalization, per-domain rollback |
58 | Sessions | Finite graphs, reports, lifecycle, history, terminal transitions, per-domain rollback |
59 | Metadata | Secret commitments, metadata records, assertion counts, `show` bindings, per-domain rollback |
60 | Intrinsics | The receipt-prefix report emitted by `verify_receipts` |
61
62 The receipt-hardened protected-state kernel inherited from Core 0.4 remains
63 responsible for source/lifecycle, packets, proofs, memories, capabilities,
64 actions, and protected rollback checks. Exact same-runtime replay is retained
65 as a separate compatibility and determinism signal.
66
67 ## Important limits
68
69 Core 0.5 does not yet independently establish:
70
71 - the general truth of all fourteen assertion forms;
72 - the exact complete cross-domain transaction projection and every associated
73 projection digest;
74 - rejection causality outside the predicates reconstructed by the component
75 verifiers;
76 - diagnostic `event_count` reconstruction;
77 - independent parsing and static checking in every path. The base, metadata,
78 and intrinsic paths still share primary frontend components.
79
80 The implementation and numerical profile remain within the Python and NumPy
81 trusted computing base. Evidence is finite-corpus executable assurance, not a
82 mechanized proof. SHA-256 binds bytes but authenticates no identity. OSL
83 capabilities are symbolic and are not an operating-system sandbox. Trusted
84 neural origin and relevance attestations remain trust roots rather than proofs
85 of semantic truth.
86
87 Read [CORE05_SEMANTIC_INDEPENDENCE_SPEC.md](CORE05_SEMANTIC_INDEPENDENCE_SPEC.md),
88 [CORE05_NUMERIC_PROFILE.md](CORE05_NUMERIC_PROFILE.md),
89 [CORE05_COMPATIBILITY.md](CORE05_COMPATIBILITY.md), and
90 [CLAIM_BOUNDARY.md](CLAIM_BOUNDARY.md) before making release claims. The native
91 trace bundle is `CORE05_TRACE_BUNDLE.jsonl`; generated summaries are
92 `CORE05_CONFORMANCE_REPORT.json`, `CORE05_SEMANTIC_REPORT.json`,
93 `CORE05_FOCUSED_REPORT.json`, and `CORE05_DISCOVERY_BRIDGE_REPORT.json`.
94
95 ## Offline verification
96
97 Install the dependency ranges from `requirements.txt`, then run the packaged
98 Core 0.5 entry point with `./verify_core05.sh` on Bash or
99 `.\verify_core05.ps1` on PowerShell. Successful verification requires no
100 network after dependencies are installed.