aurora: README branding section — expand shortlist with 7th-ferry candidates (Beacon/Lattice/Harbor/Mantle/Northstar) #261
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -143,8 +143,36 @@ public brand without clearance work is risky. | |
| continuity-preserving candidate for a public execution- | ||
| layer brand (per the LFG org + existing kernel docs). | ||
| - **Public execution brand TBD** — shortlist to research | ||
| in parallel. | ||
|
|
||
| **Combined shortlist (5th-ferry + 7th-ferry, both from | ||
| Amara).** The 5th-ferry memo (PR #235) proposed a first | ||
| shortlist; the 7th-ferry review (PR #259) proposed a second | ||
| one focused on control-plane / execution-layer candidates. | ||
| Both are preserved so Aaron's eventual brand decision has | ||
| the full option space: | ||
|
|
||
| | Candidate | Source | Why it works (verbatim from Amara) | | ||
|
There was a problem hiding this comment.
The table header says the rationale text is "verbatim from Amara," but the newly added 7th-ferry entries are paraphrased compared with Useful? React with 👍 / 👎. |
||
| |---|---|---| | ||
| | **Lucent KSK** | 5th ferry | Highest continuity with the existing repo and least ambiguity. | | ||
| | **Lucent Covenant** | 5th ferry | Emphasizes consent and mutual obligation, which the docs actually support. | | ||
| | **Halo Ledger** | 5th ferry | Preserves the "glass halo" idea without reusing Aurora directly. | | ||
|
Comment on lines
+155
to
+159
There was a problem hiding this comment. P1: The column header says the rationales are "verbatim", but at least some entries are altered vs the cited 7th-ferry source (e.g., the Beacon/Harbor rationales differ from docs/aurora/2026-04-23-amara-aurora-aligned-ksk-design-7th-ferry.md around its shortlist table). Either copy the source text exactly (including spelling) or change the header to indicate these are summaries/adaptations. |
||
| | **Meridian Gate** | 5th ferry | Neutral, infrastructural, and easier to differentiate. | | ||
| | **Consent Spine** | 5th ferry | Technically evocative, though more niche and less brand-like. | | ||
| | **Beacon** | 7th ferry | Meshes with visibility-lane vocabulary; suggests guidance, observability, operator visibility. | | ||
| | **Lattice** | 7th ferry | Layered policy, quorum, constraint composition; not defensive-sounding. | | ||
| | **Harbor** | 7th ferry | Safety, staging, revocation-friendly; not militarised. | | ||
| | **Mantle** | 7th ferry | Protective layer above execution substrate; good for "membrane around action" messaging. | | ||
| | **Northstar** | 7th ferry | Governance / guidance language; higher trademark-noise than others. | | ||
|
|
||
| **7th-ferry preferred naming pattern** (Amara): the cleanest | ||
| rhetorical stack for public explanation — **Aurora** as | ||
| vision + system architecture; **Beacon KSK** or **Lattice | ||
| KSK** as the shippable control-plane offering; **Zeta** as | ||
| the algebraic / event-processing substrate underneath. Keeps | ||
| Aurora's internal mythology while letting the public-launch | ||
| language carry trademark and category risk separately. Per | ||
| Amara 7th-ferry memo (PR #259). | ||
|
|
||
| **Brand decision is Aaron's.** Filed as Milestone M4 of the | ||
| 5th-ferry inventory. Not in scope for Otto to pick; not | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P1: Repo operational rule forbids direct contributor-name attribution in docs; use role references instead. This new section expands direct-name usage ("Amara", "Aaron"); please rewrite to role refs (e.g., "the courier-ferry author" / "the human maintainer") while preserving provenance meaning.