ObliviOS Developer portal Project site

Home / Decisions / ADR-028

Adopt a single-operator interim role model for alpha-channel signing.

Accepted, recorded 3 August 2026.

Decision
ADR-028
Date
2026-08-03
Status
AcceptedAccepted
Mentions
ADR-026
Mentioned by
ADR-029, ADR-030, ADR-110, ADR-268

Shown as written

This entry has 8 columns where the log has seven, because a cell holds the separator of the table or a column is missing. The cells follow in their order, under the label of their place.

1Decision

Adopt a single-operator interim role model for alpha-channel signing: the owner performs all five roles supply-chain-and-signing.md defines (source custodian, build operator, release reviewer, channel signer, incident lead), with compensating controls in place of true separation of duties.

2Why and evidence

AegisOS currently has one human operator. The policy's roles table assumes multiple people and states what each role "must not do alone" — that guarantee cannot be literally satisfied yet. Rather than skip the ceremony requirements (as the development channel's ADR-026 explicitly waived reproducibility) or pretend separation exists, this records the actual model in force.

3Further text

Compensating controls for this cycle: (1) independent reproduction on a genuinely separate environment (Task 4) stands in for a second build operator; (2) a written, dated self-review checklist completed after Task 5's verification and before Task 6's key generation stands in for the release-reviewer gate; (3) post-signing verification (Task 7) is run in a separate terminal session from the signing session, mirroring "the resulting signature is verified on a separate system"; (4) this entry itself is the recorded acknowledgment the ceremony-requirements section demands.

This model is explicitly valid only for the alpha channel, single-device, non-public distribution scope in this plan.

4Further text

Alpha-channel candidates in this plan are signed under a single-operator model, not full separation of duties — the integrity guarantee is weaker than the policy's default and this is a known, tracked gap, not a completed control.

5Last cell

Before any beta-channel key is proposed (supply-chain-and-signing.md requires beta ceremony access be "independently reviewed") or any stable-channel work begins (requires "designated custodians," plural) — those channels cannot use this model and need an actual second person.

Read from docs/governance/decision-log.md, entry ADR-028.