ObliviOS Developer portal Project site

Home / Decisions / ADR-171

Define a source-only publication stage that precedes the binary public beta.

Amended, recorded 15 October 2026.

Decision
ADR-171
Date
2026-10-15
Status
AmendedAmended by ADR-241, ADR-244 and ADR-248. Accepted (owner decisions of 2026-10-10, entered 2026-10-15). Work packages 1 to 8 and 10 are done (packages 2 to 5 pushed; the secret scan found nothing, freeholdos-docs exists locally and is not committed, the disclosure key is tested). Open: the site, the claim review, the legal review, an SBOM, the company logo files in the history of freeholdos-platform and the owner's read of the final set. No repository has changed visibility.
Mentions
ADR-004, ADR-170, ADR-241, ADR-244, ADR-248
Mentioned by
ADR-241, ADR-243, ADR-244, ADR-245, ADR-247, ADR-248, ADR-253, ADR-256, ADR-266

1Decision

Define a source-only publication stage that precedes the binary public beta, as designed in 2026-10-10-source-and-site-public-beta-design.md. It supersedes ADR-004 only in part.

(1) Stage: freeholdos-manifest, freeholdos-platform and freeholdos-services become public with their existing history; a new freeholdos-docs repository carries a curated copy of the documents without history; a static site and a monitored disclosure channel accompany them. No image, OTA update, update server or supported-device claim is offered to anyone but the owner. This repository stays private, and no history is rewritten.

(2) Licences and identity: Apache-2.0 for own code; each patch keeps the licence of the upstream file it changes and is never edited, so its hash and provenance stay intact; CC-BY-4.0 for documentation; the name and logo are not licensed. The copyright holder named in the NOTICE files is the owner, and the commit author address is accepted as public. AGENTS.md is replaced by CONTRIBUTING.md in the public repositories.

The long SOURCE.md of the decoy package stays public after a line-by-line review.

(3) Gates that apply to this stage: a monitored disclosure channel with a received test message, source disclosure and notices, an SBOM for the published components, trademark and privacy statements for the site, a dedicated secret scan of the full history with no unresolved finding, a claim review of every sentence of the site, the READMEs and the NOTICE files, legal review of the licence and trademark choices, and the recorded owner approval after the owner has read the final set.

Gates that apply only when binaries are offered stay as in phase-roadmap.md: firmware currency, signed production artifacts, relock, OTA and recovery evidence, compatibility, carrier and emergency evidence. (4) Legal review: the design asks for a qualified lawyer. The owner decided on 2026-10-15 that an AI agent may perform the review instead. That is not qualified counsel; the owner records, per item, the legal risk accepted when it is done.

2Why and evidence

A first stage that shows the patches, the services, the pinned upstream revisions and the decisions lets a reviewer verify the project without trusting it, without distributing software to anyone, so the binary gates (support, recovery, carrier) do not apply yet. Publishing the history is cheaper than a fresh start and keeps the patch provenance, but anything in it is copied within minutes and cannot be recalled.

3Consequences

The design lists an SBOM as a gate but no work package produces one; it is open. Publication shows an informed adversary that Duress Unlock exists, a residual risk already listed in the threat model. A public repository invites issues; whether issues are enabled is an owner decision. The name collision recorded in ADR-170 and the AI-only legal review are accepted legal risks to be recorded per item, not closed ones. The two domains held on 2026-10-10 carry the old name.

4Review when

The scan finds a secret in history; the legal review objects to a licence, the name or the AirPods-core provenance; the owner offers a binary to anyone, which triggers the full public-beta gates; ADR-004 is superseded further.

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