[FEATURE] Audit authority, code quality and documentation in docs #2

Open
opened 2026-09-12 07:57:28 +02:00 by erikinkinen · 1 comment
Owner

Problem and motivation

Audit docs throughout Phase 6. Maintain cross-component specifications, generated library API references, the TeX technical manual and their build/publication tooling.

Review each changed boundary at the final published revision. Prioritize security, reliability, then performance.

Proposed behavior and scope

Current targets: no Cargo targets. Validate the maintained scripts, workflow/templates and their tests; record Rust-only checks as individually not applicable with evidence.

There is no Cargo target. Review the API-reference generator, manual build/publication scripts, test fixtures and CI input/output ownership. Tie runtime capability and feature statements to their owning component evidence; justify each non-applicable runtime dimension separately.

Authority, security and reliability

Record each finding's affected revision, invariant, reproduction, owner, regression coverage and resolution. Report suspected vulnerabilities through SECURITY.md and keep sensitive details private. Record a result and rationale for each audit criterion, including caller responsibilities when this component has no process or Rust target.

Acceptance criteria

Checklist
  • Record origin, recipient, object, operations, delegation ceiling, lifetime and aliases for each relevant capability or caller-supplied authority-bearing value.
  • Audit ambient discovery/selectors, cwd/PATH/environment, numeric identities, inherited routes and host fallbacks; require explicit authorized intake.
  • Account for residual authority after success, error, cancellation, timeout, restart, failed transfer and teardown, including fork/exec where implemented.
  • Remove unnecessary endpoints, broad rights, duplicate aliases, provider/admin grants and debug routes.
  • Exercise stale generations, replay, pending replies, forged descriptive identity and object/path resolution races at the owned boundary.
  • Prove independent cleanup attempts and caller-specific error precedence; quarantine or terminate when retained authority cannot be accounted for.
  • Review unsafe/FFI/parser/arithmetic/lifetime/lock/publication invariants and add adversarial coverage where practical.
  • Inventory obsolete APIs, wrappers, fallback/dead paths and duplicate validators with their maintained callers.
  • Migrate callers and delete deprecated contracts/shims in a coherent signed revision graph; reject retired input versions where relevant.
  • Classify each size/count/depth/time bound as ABI, hardware, explicit resource policy or accidental limitation.
  • Test beyond removed boundaries and at allocation/ABI limits while preserving exhaustion errors, denial-of-service controls and bounded waits.
  • Keep every tracked authored code/test/script/workflow file below 1000 physical lines through thematic refactoring.
  • Run the deterministic tracked-source size gate, covering executable fixtures/generators and excluding only genuine non-code data or external payloads.
  • Audit production/test feature and symbol separation, including this repository's effect on rootd test orchestration.
  • Supply changes affecting rootd semantic surface to the maintained same-toolchain baseline; record a justified component-specific applicability result.
  • Check bootstrap ownership and development/release authority parity at this repository's producer/consumer boundary.
  • Use maintained integration#3 profiler evidence before optimizing; preserve live access checks, ownership and success criteria.
  • Audit build/CI inputs, secret handling, private outputs, symlink containment, deletion, subprocess bounds, warnings and host dependencies.
  • meaningful public/private inline documentation, crate/target missing_docs enforcement without blanket allowances or hidden-API escapes, warning-denied private-item rustdoc and an undocumented-public-API negative gate.
  • Validation: Run maintained Python/shell/template/Markdown tests and checks where present. For docs, regenerate the affected API references and build the full TeX manual with no warnings, errors or overflows; inspect changed rendered pages. Do not report absent Rust targets as passed Rust validation.
  • Documentation: update applicable README/ARCHITECTURE/ROADMAP in meta's canonical format and affected technical-manual TeX/API references; keep README evergreen and shared governance byte-identical to meta.
  • Evidence: record exact source/dependency revisions, commands, configurations, real exit status, CI run URLs and results; repeat the audit on final heads and obtain independent review of security closures. No skipped/pending/predecessor result counts as a pass.

Alternatives and tradeoffs

Refactor within the component unless shared semantics justify extracting common code. Preserve regression coverage before deleting superseded paths. Profile before optimizing, and document ABI limits, hardware limits and explicit quotas. Preserve security and reliability requirements.

Validation checkpoint — 14 September 2026: Signed Posixd 52ef820d33399490c121aad3af1409139e4a8f44 selects the proposed realm custody owner: Procd deposits an ancestor SEND-lineage revoker into its exact native generation before export and retains a nested guard for earlier realm retirement. Exported aliases descend from the nested guard; ancestor-only bypass and setup aliases must be removed before publication. Runtime producer adoption, realm byte I/O and both complete guest build generations remain open.

Its private records cannot survive userspace scheduling and own no retained source authority.

Reachable backend disposal-failure coverage, sustained invocation-workload profiling, realm producer adoption, whole-codebase authority/private-rustdoc closure and both complete EriX-in-EriX build generations remain open. No new syscall number or wire record is assigned; the existing CALL/RECV/REPLY ABI is unchanged.

Sustained invocation-workload profiling, syscall wire and fresh-buffer/fault/overlap validation, actual owned CPL3 peers, reachable backend disposal-failure coverage, realm producer adoption, whole authority/private-rustdoc closure and both complete EriX-in-EriX build generations remain open.

Every sample checks exact bytes and SEND capability bindings, authenticated origin, foreign selection, duplicate completion refusal, FIFO position reuse, one-time collection and final invocation disposal. Native syscall adapters, actual owned CPL3 peers, reachable backend disposal-failure coverage, realm adoption, full authority/private-documentation closure and both complete EriX-in-EriX build generations remain open.

Measured native invocation lookup refinement — 15 September 2026: Signed Kernel 8349d68636382cc7e25a3347f5f1df216554203a retains only numeric carrier-search positions. No successful authorization, capability or reference is cached. These are host operation wall times, not guest startup/build acceptance or a statistical guarantee. Current full-suite CI remains required; stopped cohorts are not polled again. Owned syscall wire adapters, actual owned CPL3 peers, fresh-buffer validation, reachable backend disposal-failure coverage, realm adoption, full authority/private-documentation closure and both complete EriX-in-EriX build generations remain open.

Owned invocation wire and native acceptance — 15 September 2026: Signed Kernel 5f497adaefa526108a0439e0e071717dddb85334, shared IPC de968da19898bef532ddb3b5974bb9562f51dee5, capability ABI a001a26f0eb3aebec3f5fd02a28d98f1bc23f8a0 and Integration 9030b217c490db6ad3ec60a799cb025eccbfcdb1 implement and exercise the immediate owned invocation boundary. Destination capacity and descriptive receipt capacity are independent; spare capacity acquires no authority and repeated collection cannot duplicate transfers. The real three-process CPL3 scenario passes all eight operations, full-span pointer/rights/overflow/reserved-field rejection, actual returned selectors, payload/capability/origin checks, collection after server exit and repeated receipts. A second request rejects premature relinquishment, enters draining on caller release and retires only after the exact server acknowledgment. All 162 maintained Integration helper commands pass; three prior correct concurrent-run lock refusals are retained and their sequential checks pass on unchanged executable inputs. Current full-suite acceptance remains open, as does the intermittent quota cause in Integration issue 18. Reachable backend disposal-failure coverage, broader revocation/generation-reuse scenarios, producer adoption, realm runtime, complete authority/inline-documentation audits and both full EriX-in-EriX build generations remain open.

Process-bound native acceptance — 15 September 2026: Signed Kernel 60da5858d7198185efd103f0e91e5ac2e0b63e67 implements control operation 52, checking the actual moved install grant against expected process/generation with exact rights, including zero, under existing endpoint policies. Signed Procd f1105706cc19ed024a6cca79a29abc57c90c6661 uses this operation in its actual ordinary launch-description producer while retaining the narrow SEND receipt, pending state and exact failure cleanup. All 162 Integration helpers pass after updating the exact policy assertion to require the new marker; its initial mismatch remains recorded. Typed realm bootstrap, mediator startup/readiness/configuration/seal, complete consumer image adoption, fair terminal/provider retirement, broader native disposal failures and both full EriX-in-EriX build generations remain open. The new inventory covers 76 repositories, 2,950 code files below 1,000 lines and 158 direct missing_docs crate-root gates; complete inline documentation and whole-codebase authority closure remain open.

Tracking and rollout

Signed Docs c6b0b677f16cd31cdc7555515729b376d5ff5c52 refreshes the public issue index to all 154 issues, including Integration issue 50, and records the accepted IPC platform manual CI. The two changed Markdown files pass all 45 documentation tests, 55-file Markdown lint, canonical governance/headings and exact public-link inventory checks.

Every manual source, API reference and manual build input remains identical to accepted Docs 87942ea7, whose complete local manual and CI 843/844 pass with zero final warnings. No Rust crate or runtime interface changes in this index/status update. Push CI 845 and PR CI 846 pass at this signed source. Four full logs total 752,638 bytes. Both manual jobs pass 45 tests and converge through 2,325/2,339/2,339 pages with 31/1/0 reference warnings and no final warnings or layout diagnostics. Both 55-file Markdown jobs pass. CI reports a 4,114,917-byte PDF; the artifact was not separately downloaded.

Signed Docs 87942ea7675e2a25fe3bf19f3cac19f9c5d8b1e2 specifies native IPC platform selection and hosted transport refusal, with both IPC API references generated from signed Lib-ipc 805717680d9dfb902216550a111d910807f30d23. All 2,593 ABI and 24 shim public signatures remain unchanged, as do the other 33 reference selections. Compile-target selection, local refusal, native observations and retirement evidence remain distinct.

All 45 documentation tests and 55 Markdown files pass. The complete 2,339-page manual builds in 163.82 seconds with zero final warnings. All 426,697 word boxes fit within page bounds, and three changed pages pass visual review. PDF SHA256 is 3a8e702ecf43066f4b3dde37d22d2a527fdce810bfe7e7b43f5f4912c020a6c5. Canonical governance, document headings, links, generated references and whitespace checks pass. Docs has no Cargo crate; the selected IPC source passes its strict matrix and CI 335/336.

Push CI 843 and PR CI 844 pass at this signed source. Four complete logs total 752,618 bytes. Each manual job passes 45 tests and converges through 2,325/2,339/2,339 pages; 31 first-pass and one second-pass reference warnings resolve, leaving zero final warnings and no layout diagnostics. Both Markdown jobs pass all 55 files. CI reports a 4,114,917-byte PDF; its artifact bytes were not independently inspected. The separate local PDF geometry and visual checks pass. Earlier native lifetime and runtime namespace documentation remains accepted at Docs 17b4d52a with CI 841/842. Realm adoption, separate operation-completion contracts, the whole-codebase audit and both full EriX-in-EriX builds remain open.

Signed Docs 17b4d52a9a84e0803746e3a38eb34f070bfb28a4 documents the accepted isolated native lifetime fixture and the Bootloader runtime-symbol namespace boundary. The diagnostic uses actual CPL3 owners, ordinary exit and Process-endpoint kill, exact alias/event witnesses and an explicit typed kernel-only reporter. Rust v0 defining-path recognition preserves the existing runtime namespace and exact authenticated export checks. The public coordination index contains all 153 current issues, including the three observed diagnostic/build defects.

All 45 documentation tests and 55 Markdown files pass locally. The complete 2,339-page manual builds in 164.50 seconds with zero final warnings. All 426,453 word boxes fit within page bounds; changed pages 65 and 162 pass visual review. PDF SHA256 is 2b5df3bb6edb8cbc6e667c798148c73f46a0170fc6abec7cb04615f158cf58af. Existing generated API references and renderer code are unchanged. Docs contains no Cargo crate; Rust behavior is validated in its owning repositories.

Push CI 841 and PR CI 842 pass for this signed source. Four complete logs total 752,178 bytes. Each manual job passes 45 tests and converges through 2,325/2,339/2,339 pages: 30 first-pass and one second-pass reference warnings resolve, with zero final warnings or layout diagnostics. Both Markdown jobs pass all 55 files. CI reports a 4,113,243-byte PDF; its bytes and geometry were not independently inspected. The separate local whole-PDF and two-page visual review passes. The earlier syscall/API checkpoint 28b44183 already passes CI 839/840. Kernel 03e13a78 passes CI 528/529 and Bootloader e7fa3935 passes CI 135/136; the coordinated Integration 4b65755f native VM passes the required exit and ordered unique markers. Realm adoption, provider/pending-operation completion, the full audit and both complete builds inside EriX remain open.

Current signed Docs 28b44183368c512da9c5b804f570ff497ae3b6fc passes push CI 839 and PR CI 840, completed by 08:14:56 UTC on September 14. Four complete logs total 752,154 bytes and correlate with the original workflow and build scripts. Each manual job passes 45 tests and finishes at 2,339 pages with zero final warnings; thirty first-pass and one second-pass convergence warnings resolve. Both Markdown jobs check 55 files with zero errors. CI logs report a 4,111,798-byte PDF; its artifact bytes and geometry were not independently inspected. The separate local full-PDF and five-page visual review passes. This closes renderer issue #7 only; native VM, realm producer, full audits and guest self-hosting remain open.

Signed Docs 28b44183368c512da9c5b804f570ff497ae3b6fc documents native local lifetime revocation and corrects the opaque named-field renderer (#7). Fresh original-source IPC/shim references preserve every old signature and add only the syscall assignment and safe wrapper. All 45 Docs tests, both generation checks, 55 Markdown files, canonical governance/headings/links and the 150-issue index pass. The full 2,339-page manual builds in 165.44 seconds with zero final warnings; all 426,181 word boxes fit and five selected pages pass visual review. Push CI 839 and PR CI 840 both pass as recorded above. Native VM, realm producer, complete audits and both full build generations inside EriX remain open.

  • Parent work: erix/integration#2 and #1.
  • Branch: feature/posix-compat; update linked WIP PRs after coherent signed checkpoints using canonical CONTRIBUTING.md messages.
  • Baseline revision: 3beaff9142b46e5fdb1a4245aa629a90f0735b69; refresh component/dependency heads and their own CI evidence as implementation advances.
  • Cross-repository dependencies remain full lowercase commit hashes; update the selected graph deliberately. This issue does not authorize merges, release tags or replacement of published images.

Older publication CI: Kernel 680/681 and Docs 1041 succeed. Docs 1042 reports failure: its manual job succeeds, while its Markdown job fails and the log endpoint returns HTTP 500. Seven successful job logs are retained and reviewed (1,663,075 bytes, zero final warnings); the failed job's log, exit status and cause remain unproven under Docs #11. No unchanged job was rerun. Newer separately changed Docs runs 1043/1044 pass, but do not establish a fix for this original failure. Integration 1763/1764 remain waiting.

Related records and contracts
Repository Links
kernel issue 11, issue 13
## Problem and motivation Audit `docs` throughout Phase 6. Maintain cross-component specifications, generated library API references, the TeX technical manual and their build/publication tooling. Review each changed boundary at the final published revision. Prioritize security, reliability, then performance. ## Proposed behavior and scope Current targets: no Cargo targets. Validate the maintained scripts, workflow/templates and their tests; record Rust-only checks as individually not applicable with evidence. There is no Cargo target. Review the API-reference generator, manual build/publication scripts, test fixtures and CI input/output ownership. Tie runtime capability and feature statements to their owning component evidence; justify each non-applicable runtime dimension separately. ## Authority, security and reliability Record each finding's affected revision, invariant, reproduction, owner, regression coverage and resolution. Report suspected vulnerabilities through SECURITY.md and keep sensitive details private. Record a result and rationale for each audit criterion, including caller responsibilities when this component has no process or Rust target. ## Acceptance criteria <details> <summary>Checklist</summary> - [ ] Record origin, recipient, object, operations, delegation ceiling, lifetime and aliases for each relevant capability or caller-supplied authority-bearing value. - [ ] Audit ambient discovery/selectors, cwd/PATH/environment, numeric identities, inherited routes and host fallbacks; require explicit authorized intake. - [ ] Account for residual authority after success, error, cancellation, timeout, restart, failed transfer and teardown, including fork/exec where implemented. - [ ] Remove unnecessary endpoints, broad rights, duplicate aliases, provider/admin grants and debug routes. - [ ] Exercise stale generations, replay, pending replies, forged descriptive identity and object/path resolution races at the owned boundary. - [ ] Prove independent cleanup attempts and caller-specific error precedence; quarantine or terminate when retained authority cannot be accounted for. - [ ] Review unsafe/FFI/parser/arithmetic/lifetime/lock/publication invariants and add adversarial coverage where practical. - [ ] Inventory obsolete APIs, wrappers, fallback/dead paths and duplicate validators with their maintained callers. - [ ] Migrate callers and delete deprecated contracts/shims in a coherent signed revision graph; reject retired input versions where relevant. - [ ] Classify each size/count/depth/time bound as ABI, hardware, explicit resource policy or accidental limitation. - [ ] Test beyond removed boundaries and at allocation/ABI limits while preserving exhaustion errors, denial-of-service controls and bounded waits. - [ ] Keep every tracked authored code/test/script/workflow file below 1000 physical lines through thematic refactoring. - [ ] Run the deterministic tracked-source size gate, covering executable fixtures/generators and excluding only genuine non-code data or external payloads. - [ ] Audit production/test feature and symbol separation, including this repository's effect on rootd test orchestration. - [ ] Supply changes affecting rootd semantic surface to the maintained same-toolchain baseline; record a justified component-specific applicability result. - [ ] Check bootstrap ownership and development/release authority parity at this repository's producer/consumer boundary. - [ ] Use maintained [integration#3](https://git.erikinkinen.fi/erix/integration/issues/3) profiler evidence before optimizing; preserve live access checks, ownership and success criteria. - [ ] Audit build/CI inputs, secret handling, private outputs, symlink containment, deletion, subprocess bounds, warnings and host dependencies. - [ ] meaningful public/private inline documentation, crate/target `missing_docs` enforcement without blanket allowances or hidden-API escapes, warning-denied private-item rustdoc and an undocumented-public-API negative gate. - [ ] Validation: Run maintained Python/shell/template/Markdown tests and checks where present. For docs, regenerate the affected API references and build the full TeX manual with no warnings, errors or overflows; inspect changed rendered pages. Do not report absent Rust targets as passed Rust validation. - [ ] Documentation: update applicable README/ARCHITECTURE/ROADMAP in meta's canonical format and affected technical-manual TeX/API references; keep README evergreen and shared governance byte-identical to meta. - [ ] Evidence: record exact source/dependency revisions, commands, configurations, real exit status, CI run URLs and results; repeat the audit on final heads and obtain independent review of security closures. No skipped/pending/predecessor result counts as a pass. </details> ## Alternatives and tradeoffs Refactor within the component unless shared semantics justify extracting common code. Preserve regression coverage before deleting superseded paths. Profile before optimizing, and document ABI limits, hardware limits and explicit quotas. Preserve security and reliability requirements. Validation checkpoint — 14 September 2026: Signed Posixd `52ef820d33399490c121aad3af1409139e4a8f44` selects the proposed realm custody owner: Procd deposits an ancestor SEND-lineage revoker into its exact native generation before export and retains a nested guard for earlier realm retirement. Exported aliases descend from the nested guard; ancestor-only bypass and setup aliases must be removed before publication. Runtime producer adoption, realm byte I/O and both complete guest build generations remain open. Its private records cannot survive userspace scheduling and own no retained source authority. Reachable backend disposal-failure coverage, sustained invocation-workload profiling, realm producer adoption, whole-codebase authority/private-rustdoc closure and both complete EriX-in-EriX build generations remain open. No new syscall number or wire record is assigned; the existing CALL/RECV/REPLY ABI is unchanged. Sustained invocation-workload profiling, syscall wire and fresh-buffer/fault/overlap validation, actual owned CPL3 peers, reachable backend disposal-failure coverage, realm producer adoption, whole authority/private-rustdoc closure and both complete EriX-in-EriX build generations remain open. Every sample checks exact bytes and SEND capability bindings, authenticated origin, foreign selection, duplicate completion refusal, FIFO position reuse, one-time collection and final invocation disposal. Native syscall adapters, actual owned CPL3 peers, reachable backend disposal-failure coverage, realm adoption, full authority/private-documentation closure and both complete EriX-in-EriX build generations remain open. Measured native invocation lookup refinement — 15 September 2026: Signed Kernel `8349d68636382cc7e25a3347f5f1df216554203a` retains only numeric carrier-search positions. No successful authorization, capability or reference is cached. These are host operation wall times, not guest startup/build acceptance or a statistical guarantee. Current full-suite CI remains required; stopped cohorts are not polled again. Owned syscall wire adapters, actual owned CPL3 peers, fresh-buffer validation, reachable backend disposal-failure coverage, realm adoption, full authority/private-documentation closure and both complete EriX-in-EriX build generations remain open. Owned invocation wire and native acceptance — 15 September 2026: Signed Kernel `5f497adaefa526108a0439e0e071717dddb85334`, shared IPC `de968da19898bef532ddb3b5974bb9562f51dee5`, capability ABI `a001a26f0eb3aebec3f5fd02a28d98f1bc23f8a0` and Integration `9030b217c490db6ad3ec60a799cb025eccbfcdb1` implement and exercise the immediate owned invocation boundary. Destination capacity and descriptive receipt capacity are independent; spare capacity acquires no authority and repeated collection cannot duplicate transfers. The real three-process CPL3 scenario passes all eight operations, full-span pointer/rights/overflow/reserved-field rejection, actual returned selectors, payload/capability/origin checks, collection after server exit and repeated receipts. A second request rejects premature relinquishment, enters draining on caller release and retires only after the exact server acknowledgment. All 162 maintained Integration helper commands pass; three prior correct concurrent-run lock refusals are retained and their sequential checks pass on unchanged executable inputs. Current full-suite acceptance remains open, as does the intermittent quota cause in Integration issue 18. Reachable backend disposal-failure coverage, broader revocation/generation-reuse scenarios, producer adoption, realm runtime, complete authority/inline-documentation audits and both full EriX-in-EriX build generations remain open. Process-bound native acceptance — 15 September 2026: Signed Kernel `60da5858d7198185efd103f0e91e5ac2e0b63e67` implements control operation 52, checking the actual moved install grant against expected process/generation with exact rights, including zero, under existing endpoint policies. Signed Procd `f1105706cc19ed024a6cca79a29abc57c90c6661` uses this operation in its actual ordinary launch-description producer while retaining the narrow SEND receipt, pending state and exact failure cleanup. All 162 Integration helpers pass after updating the exact policy assertion to require the new marker; its initial mismatch remains recorded. Typed realm bootstrap, mediator startup/readiness/configuration/seal, complete consumer image adoption, fair terminal/provider retirement, broader native disposal failures and both full EriX-in-EriX build generations remain open. The new inventory covers 76 repositories, 2,950 code files below 1,000 lines and 158 direct missing_docs crate-root gates; complete inline documentation and whole-codebase authority closure remain open. ## Tracking and rollout Signed Docs `c6b0b677f16cd31cdc7555515729b376d5ff5c52` refreshes the public issue index to all 154 issues, including [Integration issue 50](https://git.erikinkinen.fi/erix/integration/issues/50), and records the accepted IPC platform manual CI. The two changed Markdown files pass all 45 documentation tests, 55-file Markdown lint, canonical governance/headings and exact public-link inventory checks. Every manual source, API reference and manual build input remains identical to accepted Docs `87942ea7`, whose complete local manual and CI 843/844 pass with zero final warnings. No Rust crate or runtime interface changes in this index/status update. [Push CI 845](https://git.erikinkinen.fi/erix/docs/actions/runs/845) and [PR CI 846](https://git.erikinkinen.fi/erix/docs/actions/runs/846) pass at this signed source. Four full logs total 752,638 bytes. Both manual jobs pass 45 tests and converge through 2,325/2,339/2,339 pages with 31/1/0 reference warnings and no final warnings or layout diagnostics. Both 55-file Markdown jobs pass. CI reports a 4,114,917-byte PDF; the artifact was not separately downloaded. Signed Docs `87942ea7675e2a25fe3bf19f3cac19f9c5d8b1e2` specifies native IPC platform selection and hosted transport refusal, with both IPC API references generated from signed Lib-ipc `805717680d9dfb902216550a111d910807f30d23`. All 2,593 ABI and 24 shim public signatures remain unchanged, as do the other 33 reference selections. Compile-target selection, local refusal, native observations and retirement evidence remain distinct. All 45 documentation tests and 55 Markdown files pass. The complete 2,339-page manual builds in 163.82 seconds with zero final warnings. All 426,697 word boxes fit within page bounds, and three changed pages pass visual review. PDF SHA256 is `3a8e702ecf43066f4b3dde37d22d2a527fdce810bfe7e7b43f5f4912c020a6c5`. Canonical governance, document headings, links, generated references and whitespace checks pass. Docs has no Cargo crate; the selected IPC source passes its strict matrix and CI 335/336. [Push CI 843](https://git.erikinkinen.fi/erix/docs/actions/runs/843) and [PR CI 844](https://git.erikinkinen.fi/erix/docs/actions/runs/844) pass at this signed source. Four complete logs total 752,618 bytes. Each manual job passes 45 tests and converges through 2,325/2,339/2,339 pages; 31 first-pass and one second-pass reference warnings resolve, leaving zero final warnings and no layout diagnostics. Both Markdown jobs pass all 55 files. CI reports a 4,114,917-byte PDF; its artifact bytes were not independently inspected. The separate local PDF geometry and visual checks pass. Earlier native lifetime and runtime namespace documentation remains accepted at Docs `17b4d52a` with CI 841/842. Realm adoption, separate operation-completion contracts, the whole-codebase audit and both full EriX-in-EriX builds remain open. Signed Docs `17b4d52a9a84e0803746e3a38eb34f070bfb28a4` documents the accepted isolated native lifetime fixture and the Bootloader runtime-symbol namespace boundary. The diagnostic uses actual CPL3 owners, ordinary exit and Process-endpoint kill, exact alias/event witnesses and an explicit typed kernel-only reporter. Rust v0 defining-path recognition preserves the existing runtime namespace and exact authenticated export checks. The public coordination index contains all 153 current issues, including the three observed diagnostic/build defects. All 45 documentation tests and 55 Markdown files pass locally. The complete 2,339-page manual builds in 164.50 seconds with zero final warnings. All 426,453 word boxes fit within page bounds; changed pages 65 and 162 pass visual review. PDF SHA256 is `2b5df3bb6edb8cbc6e667c798148c73f46a0170fc6abec7cb04615f158cf58af`. Existing generated API references and renderer code are unchanged. Docs contains no Cargo crate; Rust behavior is validated in its owning repositories. [Push CI 841](https://git.erikinkinen.fi/erix/docs/actions/runs/841) and [PR CI 842](https://git.erikinkinen.fi/erix/docs/actions/runs/842) pass for this signed source. Four complete logs total 752,178 bytes. Each manual job passes 45 tests and converges through 2,325/2,339/2,339 pages: 30 first-pass and one second-pass reference warnings resolve, with zero final warnings or layout diagnostics. Both Markdown jobs pass all 55 files. CI reports a 4,113,243-byte PDF; its bytes and geometry were not independently inspected. The separate local whole-PDF and two-page visual review passes. The earlier syscall/API checkpoint `28b44183` already passes CI 839/840. Kernel `03e13a78` passes CI 528/529 and Bootloader `e7fa3935` passes CI 135/136; the coordinated Integration `4b65755f` native VM passes the required exit and ordered unique markers. Realm adoption, provider/pending-operation completion, the full audit and both complete builds inside EriX remain open. Current signed Docs `28b44183368c512da9c5b804f570ff497ae3b6fc` passes [push CI 839](https://git.erikinkinen.fi/erix/docs/actions/runs/839) and [PR CI 840](https://git.erikinkinen.fi/erix/docs/actions/runs/840), completed by 08:14:56 UTC on September 14. Four complete logs total 752,154 bytes and correlate with the original workflow and build scripts. Each manual job passes 45 tests and finishes at 2,339 pages with zero final warnings; thirty first-pass and one second-pass convergence warnings resolve. Both Markdown jobs check 55 files with zero errors. CI logs report a 4,111,798-byte PDF; its artifact bytes and geometry were not independently inspected. The separate local full-PDF and five-page visual review passes. This closes renderer issue #7 only; native VM, realm producer, full audits and guest self-hosting remain open. Signed Docs `28b44183368c512da9c5b804f570ff497ae3b6fc` documents native local lifetime revocation and corrects the opaque named-field renderer (#7). Fresh original-source IPC/shim references preserve every old signature and add only the syscall assignment and safe wrapper. All 45 Docs tests, both generation checks, 55 Markdown files, canonical governance/headings/links and the 150-issue index pass. The full 2,339-page manual builds in 165.44 seconds with zero final warnings; all 426,181 word boxes fit and five selected pages pass visual review. [Push CI 839](https://git.erikinkinen.fi/erix/docs/actions/runs/839) and [PR CI 840](https://git.erikinkinen.fi/erix/docs/actions/runs/840) both pass as recorded above. Native VM, realm producer, complete audits and both full build generations inside EriX remain open. - Parent work: https://git.erikinkinen.fi/erix/integration/issues/2 and https://git.erikinkinen.fi/erix/docs/issues/1. - Branch: `feature/posix-compat`; update linked WIP PRs after coherent signed checkpoints using canonical CONTRIBUTING.md messages. - Baseline revision: `3beaff9142b46e5fdb1a4245aa629a90f0735b69`; refresh component/dependency heads and their own CI evidence as implementation advances. - Cross-repository dependencies remain full lowercase commit hashes; update the selected graph deliberately. This issue does not authorize merges, release tags or replacement of published images. Older publication CI: Kernel [680](https://git.erikinkinen.fi/erix/kernel/actions/runs/680)/[681](https://git.erikinkinen.fi/erix/kernel/actions/runs/681) and Docs [1041](https://git.erikinkinen.fi/erix/docs/actions/runs/1041) succeed. Docs [1042](https://git.erikinkinen.fi/erix/docs/actions/runs/1042) reports failure: its manual job succeeds, while its Markdown job fails and the log endpoint returns HTTP 500. Seven successful job logs are retained and reviewed (1,663,075 bytes, zero final warnings); the failed job's log, exit status and cause remain unproven under [Docs #11](https://git.erikinkinen.fi/erix/docs/issues/11). No unchanged job was rerun. Newer separately changed Docs runs 1043/1044 pass, but do not establish a fix for this original failure. Integration [1763](https://git.erikinkinen.fi/erix/integration/actions/runs/1763)/[1764](https://git.erikinkinen.fi/erix/integration/actions/runs/1764) remain waiting. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | kernel | [issue 11](https://git.erikinkinen.fi/erix/kernel/issues/11), [issue 13](https://git.erikinkinen.fi/erix/kernel/issues/13) | </details>
erikinkinen changed title from [FEATURE] [P02.R07] Audit authority, code quality and documentation in docs to [FEATURE] Audit authority, code quality and documentation in docs 2026-09-12 08:02:12 +02:00
Author
Owner

The manual correction now describes AES's constant-time dependency and erasure accurately: normal destruction clears its owned expanded schedule, and the XTS tweak uses an owned secret buffer. Caller storage, temporary copies and scratch buffers have separate lifetimes. This corrects the documentation; it does not change the cryptographic APIs or consumer selections.

The [manual correction](https://git.erikinkinen.fi/erix/docs/commit/e555a7055fa2574c892d981dfeb9a0c692a1a90a) now describes AES's constant-time dependency and erasure accurately: normal destruction clears its owned expanded schedule, and the XTS tweak uses an owned secret buffer. Caller storage, temporary copies and scratch buffers have separate lifetimes. This corrects the documentation; it does not change the cryptographic APIs or consumer selections.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:37 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/docs#2
No description provided.