[FEATURE] Own derived inputs for the Timed clock contract #429

Open
opened 2026-11-06 15:55:35 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

The Timed clock contract builds a fixed host test harness from selected Timed and LibIPC sources. The maintained Cargo consumer admits original catalog workspaces, so this derived harness needs its own input owner rather than being presented as an original workspace.

Proposed behavior and scope

Add a narrow clock-harness producer bound to the actual selected Cargo consumer. It reads authenticated original source blobs and creates only the fixed contract, adapters and transformed source tree. Preserve the complete existing clock-contract cases and both standalone and catalog-backed operation.

Authority, security and reliability

The producer retains the original consumer and actual derived file/directory owners for its full lifetime. Before every command, check the complete derived namespace, current bytes, original source bindings, selected tools/configuration, dependency attribution and lock compatibility. Invoke only the fixed transformed manifest through a dedicated admitted command route; keep the generic original-workspace validator unchanged.

Registration, partial acquisition, reentry, first failure, cancellation and teardown must remain accounted for. A failed or retired producer cannot admit another command. Paths, hashes, metadata and receipts describe inputs but cannot reconstruct their owners. Preserve the original finite time, output and input budgets.

Acceptance criteria

  • Document and implement the original-to-derived ownership boundary.
  • Preserve the complete clock contract and source-policy checks.
  • Support both standalone and catalog-backed selected sources.
  • Verify actual Cargo metadata, unchanged dependency attribution and compatible locks for the derived harness.
  • Cover substitution, mutation, partial acquisition, reentry, cancellation and retirement refusals.
  • Run the real derived harness and required formatting, lint and documentation checks without warnings.
  • Keep host contract evidence separate from native deadline and guest acceptance.

Alternatives and tradeoffs

Weakening the original-workspace validator would blur original and derived inputs. Standalone-only support would leave catalog-backed operation incomplete. A fixed producer adds explicit ownership work while keeping the generic validator and dependency boundary intact. Lock compatibility must be established with actual Cargo observations.

Tracking and rollout

Build on the retained compilation inputs in #425 and the current source-consumer stack through #427. Implement on a separate feature branch and remove the old command-owner facade from this contract path. Track Alpha 1 acceptance in #65.

## Problem and motivation The Timed clock contract builds a fixed host test harness from selected Timed and LibIPC sources. The maintained Cargo consumer admits original catalog workspaces, so this derived harness needs its own input owner rather than being presented as an original workspace. ## Proposed behavior and scope Add a narrow clock-harness producer bound to the actual selected Cargo consumer. It reads authenticated original source blobs and creates only the fixed contract, adapters and transformed source tree. Preserve the complete existing clock-contract cases and both standalone and catalog-backed operation. ## Authority, security and reliability The producer retains the original consumer and actual derived file/directory owners for its full lifetime. Before every command, check the complete derived namespace, current bytes, original source bindings, selected tools/configuration, dependency attribution and lock compatibility. Invoke only the fixed transformed manifest through a dedicated admitted command route; keep the generic original-workspace validator unchanged. Registration, partial acquisition, reentry, first failure, cancellation and teardown must remain accounted for. A failed or retired producer cannot admit another command. Paths, hashes, metadata and receipts describe inputs but cannot reconstruct their owners. Preserve the original finite time, output and input budgets. ## Acceptance criteria - [ ] Document and implement the original-to-derived ownership boundary. - [ ] Preserve the complete clock contract and source-policy checks. - [ ] Support both standalone and catalog-backed selected sources. - [ ] Verify actual Cargo metadata, unchanged dependency attribution and compatible locks for the derived harness. - [ ] Cover substitution, mutation, partial acquisition, reentry, cancellation and retirement refusals. - [ ] Run the real derived harness and required formatting, lint and documentation checks without warnings. - [ ] Keep host contract evidence separate from native deadline and guest acceptance. ## Alternatives and tradeoffs Weakening the original-workspace validator would blur original and derived inputs. Standalone-only support would leave catalog-backed operation incomplete. A fixed producer adds explicit ownership work while keeping the generic validator and dependency boundary intact. Lock compatibility must be established with actual Cargo observations. ## Tracking and rollout Build on the retained compilation inputs in #425 and the current source-consumer stack through #427. Implement on a separate feature branch and remove the old command-owner facade from this contract path. Track Alpha 1 acceptance in #65.
erikinkinen added this to the Alpha 1 milestone 2026-11-06 15:55:35 +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#429
No description provided.