[FEATURE] Publish manual artifacts through explicit owned inputs #16

Open
opened 2026-10-14 10:23:48 +02:00 by erikinkinen · 3 comments
Owner

Problem and motivation

Manual publication needs reviewable artifact, source, credential and recipient inputs, with one bounded operation and clear failure records.

Proposed behavior and scope

Use an explicit request for the repository, Git ref, full source commit, artifact/checksum, selected HTTPS recipient and CA, and finite resource budgets. The protected CI adapter admits its one configured secret and supplies sealed read-only inputs. The publisher borrows the actual original owner; it cannot recreate that owner's clock or close the adapter's resources.

Keep main/nightly, tag and branch routing explicit. Encode branch artifact tags reversibly in a namespace separate from the older branch tags. Migrate callers together and remove superseded interfaces.

Authority, security and reliability

Select complete procedure and tool inputs before execution. Keep the publisher environment minimal and authentication out of arguments, URLs and diagnostic records. Validate repository, ref, commit and response framing before mutations. Refuse foreign recipients, redirects, incomplete provenance and uncertain cleanup. Preserve the first failure and every independent cleanup result; unknown delivery cannot authorize replay.

These are host publication procedures. They do not establish EriX runtime or guest admission.

Acceptance criteria

  • Implement the explicit procedure, protected CI adapter and coherent caller migration.
  • Cover routing, framing, malformed responses, provenance, budgets, cancellation and independent cleanup.
  • Exercise real TLS and hostname/certificate refusal using contained local fixtures and fake credentials.
  • Document the contract and keep authored modules below 1,000 physical lines.
  • Publish the reviewed change and reconcile remaining legacy routing requirements.

Alternatives and tradeoffs

Keeping the actual bootstrap owner alive preserves its original deadline and cleanup obligations. Explicit borrowed inputs make each resource's holder and retirement rights reviewable.

Tracking and rollout

Documentation audit, manual review, CI compatibility, phase completion. Keep detailed private authority findings separate from this interface proposal.

## Problem and motivation Manual publication needs reviewable artifact, source, credential and recipient inputs, with one bounded operation and clear failure records. ## Proposed behavior and scope Use an explicit request for the repository, Git ref, full source commit, artifact/checksum, selected HTTPS recipient and CA, and finite resource budgets. The protected CI adapter admits its one configured secret and supplies sealed read-only inputs. The publisher borrows the actual original owner; it cannot recreate that owner's clock or close the adapter's resources. Keep main/nightly, tag and branch routing explicit. Encode branch artifact tags reversibly in a namespace separate from the older branch tags. Migrate callers together and remove superseded interfaces. ## Authority, security and reliability Select complete procedure and tool inputs before execution. Keep the publisher environment minimal and authentication out of arguments, URLs and diagnostic records. Validate repository, ref, commit and response framing before mutations. Refuse foreign recipients, redirects, incomplete provenance and uncertain cleanup. Preserve the first failure and every independent cleanup result; unknown delivery cannot authorize replay. These are host publication procedures. They do not establish EriX runtime or guest admission. ## Acceptance criteria - [ ] Implement the explicit procedure, protected CI adapter and coherent caller migration. - [ ] Cover routing, framing, malformed responses, provenance, budgets, cancellation and independent cleanup. - [ ] Exercise real TLS and hostname/certificate refusal using contained local fixtures and fake credentials. - [ ] Document the contract and keep authored modules below 1,000 physical lines. - [ ] Publish the reviewed change and reconcile remaining legacy routing requirements. ## Alternatives and tradeoffs Keeping the actual bootstrap owner alive preserves its original deadline and cleanup obligations. Explicit borrowed inputs make each resource's holder and retirement rights reviewable. ## Tracking and rollout [Documentation audit](https://git.erikinkinen.fi/erix/docs/issues/2), [manual review](https://git.erikinkinen.fi/erix/docs/pulls/4), [CI compatibility](https://git.erikinkinen.fi/erix/integration/issues/113), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). Keep detailed private authority findings separate from this interface proposal.
Author
Owner

The first actual contained TLS case stopped at bootstrap startup before HTTP. Issue 17 tracks the missing standard-library selection and complete-cohort loading coverage. The original failed case and cleanup records remain retained; implementation continues on a separately reviewed correction.

The first actual contained TLS case stopped at bootstrap startup before HTTP. [Issue 17](https://git.erikinkinen.fi/erix/docs/issues/17) tracks the missing standard-library selection and complete-cohort loading coverage. The original failed case and cleanup records remain retained; implementation continues on a separately reviewed correction.
Author
Owner

0f53e8a5 replaces the manual shell builder with explicit engine, runtime, source and process-owner inputs. Maintained CLI and CI callers now deliver real child output through the bounded owner, retain failed-pass diagnostics and require all auxiliary files to converge before producing a PDF. The strict three-pass host render completes with zero final warnings. Publisher migration remains separate under #20.

`0f53e8a5` replaces the manual shell builder with explicit engine, runtime, source and process-owner inputs. Maintained CLI and CI callers now deliver real child output through the bounded owner, retain failed-pass diagnostics and require all auxiliary files to converge before producing a PDF. The strict three-pass host render completes with zero final warnings. Publisher migration remains separate under #20.
Author
Owner

14e36d18 replaces the shell artifact publisher with explicit source, endpoint, CA and credential inputs. A single bounded owner covers publication and retirement; uncertain cleanup prevents replacement. The broader repository authority audit remains open.

The original CI builds the manual, then publication fails. #23 tracks the selected credential and missing startup diagnostic.

`14e36d18` replaces the shell artifact publisher with explicit source, endpoint, CA and credential inputs. A single bounded owner covers publication and retirement; uncertain cleanup prevents replacement. The broader repository authority audit remains open. The original CI builds the manual, then publication fails. [#23](https://git.erikinkinen.fi/erix/docs/issues/23) tracks the selected credential and missing startup diagnostic.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:40 +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#16
No description provided.