generated from erix/meta
[FEATURE] Audit authority, code quality and documentation in lib-service #1
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-service#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
Audit
lib-servicethroughout Phase 6. Resolve exactly one service target through a caller-held named endpoint and validate its transferred capability receipt.Review each changed boundary at the final published revision. Prioritize security, reliability, then performance.
Proposed behavior and scope
Current inventory: 1 Cargo target (1 lib); manifests:
Cargo.toml. Include explicit and automatically discovered targets, supported features and target-specific configurations.Trace authority-bearing inputs through callers and public APIs. Confirm that the library acquires no service, hardware or host authority implicitly. Review startup, teardown and Rootd parity at the caller boundary when this crate owns no process, and justify each applicability decision.
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
missing_docsenforcement without blanket allowances or hidden-API escapes, warning-denied private-item rustdoc and an undocumented-public-API negative gate.cargo fmt --all -- --check, strict Clippy, unit/doctests and warning-denied builds/rustdoc for every owned crate/target under default and all valid feature, freestanding/host, SMP and profile combinations; test mutually exclusive combinations separately. Add focused VM regressions for runtime behavior and observe the older catalog and unit tests at the exact published heads.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.
The observed push CI run is successful; complete log classification and a review-triggered run remain required.
Process-bound native acceptance — 15 September 2026: The signed helper checkpoint now passes both push and review CIs with complete warning-free logs. Component acceptance does not close complete realm or guest-build work.
The mediator class cannot use ordinary start, immediate commit, TTY provisioning, powerbox installation or automatic restart. Procd has forty native binary builds and six new mediator refusal/cleanup regressions. No Posixd executable or coordinated realm VM acceptance is claimed. Actual grant-return provisioning, authenticated caller ownership, typed startup memory/inventory, readiness, configuration/seal, client I/O, fair retirement, complete consumer image adoption and both full guest build generations remain open.
Actual grant-return provisioning, authenticated receiver readiness, configuration/seal, client I/O, fair retirement, whole-codebase authority/documentation closure and both complete guest build generations remain required. No runnable Posixd realm or guest-build acceptance is claimed.
Native producer/consumer migration, matching VM execution and full guest builds remain separate acceptance gates.
Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.
Returned-grant shared contract checkpoint — 18 September 2026: Signed revision
3ac92f42cb9919abe06b63d07ac42b1c9fd68ea7is pushed. The coherent immutable dependency graph adopts the checked returned-grant bootstrap contract. Local runtime policy is unchanged. Default/all-feature development and release units, strict host/native Clippy, native builds and private-item rustdoc pass. Formatting and Markdown checks pass. Original CI 71 and CI 72 passes; all four terminal logs are complete (49,928 bytes), without warnings. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.
Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.
Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.
Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.
Actual admission dispatch, coordinated consumer VMs, runnable mediators and both full builds inside EriX remain separate open acceptance requirements.
Tracking and rollout
Coordinated native consumer acceptance remains separate in PR2.
Each of the four default/all-feature development/release selections passes 15 tests/doctests. Formatting, strict host/native Clippy, warning-denied builds, private rustdoc, Markdown and exact original dependency checks pass with zero warnings.
Actual running mediator readiness/retirement, complete service-image acceptance, configuration/seal, client I/O and both required guest rebuilds remain open.
Tracking: owning issue, WIP PR and Phase 6 acceptance.
Native mediator execution, coordinated runtime acceptance and full guest builds remain open.
Runtime dependency alignment — 15 September 2026
Coherent product catalog adoption and product VM acceptance remain pending.
Validated mediator constructor adoption — 15 September 2026
A refusal never falls back to operation 32.
The existing shared graph follows signed IPC 7c771205 and applicable capability ABI 2d6b1283 through original Git objects; no dependency or helper authority is added.
Runtime-image adoption, authenticated grant return, guarded bootstrap routes, private execution, receiver readiness, configuration/seal, client I/O, fair retirement and both full guest build generations remain open.
Coordinated actual consumers and matching native execution remain open under Kernel design 19. This dependency/wire checkpoint does not establish complete lifecycle acceptance or either full EriX build generation.
No local API or capability policy changes. Actual service consumer and coherent full VM adoption remain open in phase completion.
Related records and contracts
[FEATURE] [P02.R51] Audit authority, code quality and documentation in lib-serviceto [FEATURE] Audit authority, code quality and documentation in lib-serviceerikinkinen referenced this issue from erix/integration2026-09-19 23:04:20 +02:00