…es (#92) ## Summary Foundation/guardrail changes toward the core implementation, not a release or a claim that all compliance work is complete. Refs #2, #4. Neither issue should be automatically closed by this PR. ### Core implementation - Retain LMDB; document the storage decision, proof boundaries, and remaining issue #4 closure criteria in ADR-0006. - Add a bounded LMDB primitive with atomic session/event/sequence updates, explicit schema version, default-sync commits, copied-out reads, and storage-error handling. - Test abort/reopen, SIGKILL before and after commit, map exhaustion, and concurrent independent writers. - Harden sampling with checked observation/reduction paths, wide arithmetic, reset detection, and selected-device disk utilization rather than summed utilization. - Add a finite control-policy kernel and a filesystem-only OFF bypass helper. These are not a deployed controller. - Replace placeholder `just test` success with real, timeout-bounded tests; configure Debug and ReleaseSafe CI coverage. Make the unimplemented E2E command fail explicitly. ### Security and repository discipline - Repair stale structure/workflow validation requirements and checks that hid failures. - Make local security recipes reject missing tools and propagate scanner failures. - Replace misleading template security guidance with project-specific reporting, privacy and isolation guidance. - Correct template completion claims in project state, add development setup documentation, and fix duplicate Rust CI configuration. - Record the licensing conflicts and outstanding compliance work without changing existing SPDX/copyright declarations, LICENSE, LICENSES/, or REUSE.toml. ## Validation Executed locally with Zig 0.15.2 and LMDB 0.9.33: - `LMDB_PREFIX=/home/user/toolchains/lmdb-install just test` — 19 tests pass. - Same command with `-O ReleaseSafe` — 19 tests pass. - `just validate` — passes with documented warnings (Idris2 unavailable and broad placeholder detection). - `bash tests/workflows/compliance_regression_test.sh` — passes. - ShellCheck on reviewed validation/state/core-test scripts and `tests/workflows/*.sh` — passes. - Zig formatting and `git diff --check` — pass. - `just e2e` — expected failure: live monitor/hook acceptance suite is not implemented. The local LMDB prefix is an external tool installation, not a repository dependency path. CI uses the Ubuntu LMDB development package. Hosted CI results must be reviewed separately. ## Known limitations / review gates - **Issue #2 remains manual owner-only.** REUSE still reports missing metadata. This PR does not authorize or perform relicensing, blanket attribution, or modification of third-party headers. - **Issue #4 remains open.** Live monitor ownership, session collection/autoconnection, bounded IPC/backpressure, retry deduplication, retention, and isolated resource-pressure acceptance tests are still required. - LMDB writer-lock/fsync operations are not bounded-time. Hooks must not invoke the primitive synchronously on their blocking path. - Process-crash tests do not establish host/VM/power-loss durability. - Type-theory repositories were reviewed for potential proof applications; no new mechanised proofs or correspondence to Zig are claimed. - Idris2 and security scanner checks remain unrun; branch-protection inspection was denied by integration permissions. Existing scanner-workflow risks are documented in COMPLIANCE-REVIEW.adoc. - No global hooks, live load-shedding, memory balloon, or release is enabled. ## Review entry points - `docs/decisions/0006-ledger-and-proof-boundaries.adoc` - `docs/governance/COMPLIANCE-REVIEW.adoc` - `src/ledger/README.adoc` Co-authored-by: hyperpolymath <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>

Uh oh!

Core: Zig signal sampler + shared crash-safe LMDB ledger #4

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions