[BUG] Align factory documentation with initial-result authority #115

Closed
opened 2026-10-13 03:01:27 +02:00 by erikinkinen · 1 comment
Owner

Summary

Several factory documents omit the WRITE right used for initial-result retirement. They also retain the superseded receiver-only intake description and conflate RCF1 minor nine with RCP1 minor ten. This makes the documented producer/receiver contract disagree with the implemented one. The finding is a documentation defect; no runtime authority breach is established.

Reproduction

Read the factory paragraphs in Integration's architecture, the manual's client lifecycle, and the Launchd/Procd factory documents. Compare them with Posixd's current factory contract and the role constants and receiver/retirement checks they reference. A clean source checkout reproduces the text mismatch without running a guest.

Expected and actual behavior

Document the complete transition: Procd source READ/WRITE/MINT/GRANT (0xc03), unique Launchd delivery and initial Posixd READ/WRITE/MINT (0x803), then READ/MINT (0x801) only after genuine initial-result retirement and fresh inventory/native READ. Kernel removes spent WRITE and the scalar together from the original binding. Refused join/detach retains both; uncertain retirement retains the original cleanup duty and metadata reconciliation cannot recreate a scalar or grant.

Some current prose instead describes READ/MINT-only delivery or receiver-only intake. Correct the wire versions, pull-reply rustdoc, producer/receiver descriptions and manual together, preserving all layouts and runtime checks.

Environment and identity

  • Components: Integration 3fe7fce618, Docs e980af91c77da05d2168476888550f82e0ccdff3 and Posixd 8e9039b5f59ee04b33b5369f38d4bfe4d31c17df, with their selected factory source graph.
  • Image/runtime: source-document comparison; no image, guest or new grant is required.
  • Hardware/toolchain: not involved in reproducing the text discrepancy.
  • Input and authority: ordinary source reads; runtime permissions remain unchanged.
  • Last correct complete documentation revision: not established.

Evidence and prior checks

The role masks, initial receiver checks and spent-WRITE retirement implementation agree. The manual's native ownership chapter already describes that transition; the older factory intake and codec paragraphs do not. Link corrected source and document revisions here when the coordinated repair is published.

Tracking

Related contracts: native factory design, native retirement, join/detach, Integration review, manual review and Phase 6 completion.

## Summary Several factory documents omit the WRITE right used for initial-result retirement. They also retain the superseded receiver-only intake description and conflate RCF1 minor nine with RCP1 minor ten. This makes the documented producer/receiver contract disagree with the implemented one. The finding is a documentation defect; no runtime authority breach is established. ## Reproduction Read the factory paragraphs in [Integration's architecture](https://git.erikinkinen.fi/erix/integration/src/commit/3fe7fce618cbd68d5576a470fcb9fa45268fc7ab/ARCHITECTURE.md), [the manual's client lifecycle](https://git.erikinkinen.fi/erix/docs/src/commit/e980af91c77da05d2168476888550f82e0ccdff3/manual/7-system-service-apis/17b-realm-client-lifecycle.tex), and the Launchd/Procd factory documents. Compare them with [Posixd's current factory contract](https://git.erikinkinen.fi/erix/posixd/src/commit/8e9039b5f59ee04b33b5369f38d4bfe4d31c17df/docs/client-thread-factory.md) and the role constants and receiver/retirement checks they reference. A clean source checkout reproduces the text mismatch without running a guest. ## Expected and actual behavior Document the complete transition: Procd source READ/WRITE/MINT/GRANT (0xc03), unique Launchd delivery and initial Posixd READ/WRITE/MINT (0x803), then READ/MINT (0x801) only after genuine initial-result retirement and fresh inventory/native READ. Kernel removes spent WRITE and the scalar together from the original binding. Refused join/detach retains both; uncertain retirement retains the original cleanup duty and metadata reconciliation cannot recreate a scalar or grant. Some current prose instead describes READ/MINT-only delivery or receiver-only intake. Correct the wire versions, pull-reply rustdoc, producer/receiver descriptions and manual together, preserving all layouts and runtime checks. ## Environment and identity - Components: Integration 3fe7fce618cbd68d5576a470fcb9fa45268fc7ab, Docs e980af91c77da05d2168476888550f82e0ccdff3 and Posixd 8e9039b5f59ee04b33b5369f38d4bfe4d31c17df, with their selected factory source graph. - Image/runtime: source-document comparison; no image, guest or new grant is required. - Hardware/toolchain: not involved in reproducing the text discrepancy. - Input and authority: ordinary source reads; runtime permissions remain unchanged. - Last correct complete documentation revision: not established. ## Evidence and prior checks The role masks, initial receiver checks and spent-WRITE retirement implementation agree. The manual's native ownership chapter already describes that transition; the older factory intake and codec paragraphs do not. Link corrected source and document revisions here when the coordinated repair is published. ## Tracking Related contracts: [native factory design](https://git.erikinkinen.fi/erix/kernel/issues/47), [native retirement](https://git.erikinkinen.fi/erix/kernel/issues/52), [join/detach](https://git.erikinkinen.fi/erix/posixd/issues/41), [Integration review](https://git.erikinkinen.fi/erix/integration/pulls/12), [manual review](https://git.erikinkinen.fi/erix/docs/pulls/4) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

The coordinated correction is published in LibIPC, LibCapABI, Procd, Launchd, Exsh and the manual. The documents now distinguish source 0xc03, initial receipt 0x803, and 0x801 only after native initial-result retirement and fresh inventory/READ. They also distinguish RCF1 1.9 from RCP1 1.10. The LibIPC reference is regenerated from the corrected signed source, with current startup, arena and provisioning sizes. This resolves the documentation discrepancy; ordinary-thread and guest-build requirements remain open.

The coordinated correction is published in [LibIPC](https://git.erikinkinen.fi/erix/lib-ipc/commit/afbf16910e5798af849057984abee5149a006824), [LibCapABI](https://git.erikinkinen.fi/erix/lib-capabi/commit/347a7e9a857e8a4d92acc8aff73876228336707d), [Procd](https://git.erikinkinen.fi/erix/procd/commit/9b79817622b49b46c7aad9604fbf4bc19d02a4f6), [Launchd](https://git.erikinkinen.fi/erix/launchd/commit/c502599b29c168582fe28dbdab8a86bcef7ec56e), [Exsh](https://git.erikinkinen.fi/erix/exsh/commit/f8b4cc74eec2caf3c4fe7aef1d47f3aa9de11ab8) and [the manual](https://git.erikinkinen.fi/erix/docs/commit/8ee44cc676465ae2a60192f7cdfc856e48a4944a). The documents now distinguish source `0xc03`, initial receipt `0x803`, and `0x801` only after native initial-result retirement and fresh inventory/READ. They also distinguish RCF1 1.9 from RCP1 1.10. The LibIPC reference is regenerated from the corrected signed source, with current startup, arena and provisioning sizes. This resolves the documentation discrepancy; ordinary-thread and guest-build requirements remain open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:15 +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/integration#115
No description provided.