docs: Frontier rename candidate analysis — advisory (Otto-170) by AceHack · Pull Request #349 · Lucent-Financial-Group/Zeta

AceHack · 2026-04-24T09:44:26Z

Summary

Advisory analysis of the six Otto-168 rename candidates applying naming-expert rubric + WebSearch trademark + agentic-AI-platform conflict scan.

Verdict table

Candidate	Verdict
Zora	NOT VIABLE — active Deloitte vs Zora Labs litigation over "Zora AI"
Starboard	VIABLE — no direct agentic-AI-platform conflict found
Bridge	NOT RECOMMENDED — generic, poor searchability
Horizon	NOT VIABLE — Topia Horizon + Eagleview Horizon in 2026
Vantage	NOT RECOMMENDED — Palantir Vantage
Aurora	NOT VIABLE — conflates with factory governance layer + AWS/NEAR crowding

Key finding

"Zora" has active trademark litigation between Zora Labs (Ethereum NFT) and Deloitte Consulting (Zora AI agentic-AI platform, integrated with Oracle + SAP Joule). Federal judge denied preliminary injunction 2025-2026; dispute unresolved. Adopting Zora puts the factory between two parties already in combat over the same word in the same market. The frontier-ux-zora-evolution-*.md filename was chosen before this conflict was visible.

Starboard analysis

Only candidate with zero agentic-AI-platform conflict. Existing Starboard products (reservation system + interactive whiteboards) operate in adjacent but distinct markets. Naming-expert discipline pass on denotation / connotation / boundary / searchability / longevity.

Non-actions

Does NOT pick a name (Aaron's call per Otto-168).
Does NOT commit to Starboard specifically.
Does NOT replace formal trademark clearance (TSDR + vendor-DB search would be required pre-launch).
Adjacent candidate categories listed for Aaron consideration (Star-Trek bridge vocab, navigation terms, ship-architecture).

Test plan

Markdownlint clean.
Research-grade under docs/research/.
No BACKLOG tail touch.

🤖 Generated with Claude Code

…on (Otto-170) Applies naming-expert skill rubric + WebSearch trademark / agentic-AI-platform conflict scan to the six Otto-168 rename candidates. Results: | Candidate | Verdict | |-----------|---------| | Zora | NOT VIABLE (Deloitte Zora AI active litigation with Zora Labs) | | Starboard | VIABLE (no direct agentic-AI conflict) | | Bridge | NOT RECOMMENDED (generic, poor searchability) | | Horizon | NOT VIABLE (Topia Horizon + Eagleview Horizon in 2026) | | Vantage | NOT RECOMMENDED (Palantir Vantage) | | Aurora | NOT VIABLE (conflates with factory governance layer + AWS/NEAR crowding) | Key finding: "Zora" has ACTIVE TRADEMARK LITIGATION — Zora Labs vs Deloitte over Zora AI. Federal judge denied preliminary injunction 2025-2026 but dispute is unresolved. The existing `frontier-ux-zora-evolution-*.md` filename was incidentally chosen before this conflict was visible; adopting Zora formally would put the factory between two parties already in legal combat over the same word in the same market. Starboard emerges as the only VIABLE candidate with zero agentic-AI-platform conflict. Existing Starboard products (Starboard Suite reservation system, StarBoard Solution interactive whiteboards) operate in adjacent-but-distinct markets; brand confusion risk low. Explicit non-actions preserved: - Does NOT pick a name; Aaron is concept owner. - Does NOT commit to Starboard specifically. - Does NOT escalate to immediate-tick work. - Does NOT replace formal trademark clearance. - Does NOT predict future conflicts (agentic-AI namespace crowding rapidly in 2026). Lists adjacent candidate categories (Star-Trek bridge vocab, navigation terms, ship-architecture) in case Aaron wants fresh names not on the original list. Composes with Otto-168 BACKLOG row (action step #3), frontier-ux-zora-evolution design doc (primary rename target), docs/definitions/KSK.md (Aurora/Zeta/KSK naming triangle), naming-expert skill rubric. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

chatgpt-codex-connector · 2026-04-24T09:44:32Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Copilot

Pull request overview

Adds a research-grade advisory document analyzing candidate names for the “Frontier UI” rename, focusing on naming-conflict/trademark risk and agentic-AI-platform namespace collisions.

Changes:

Introduces a new candidate-analysis doc under docs/research/ covering six rename options and a summary verdict table.
Adds cross-references to related repo artifacts (BACKLOG row, UX doc, naming rubric, KSK naming triangle).

Copilot · 2026-04-24T09:48:06Z

+# Frontier UI Rename — Candidate Analysis (Otto-170)
+
+**Status:** research-grade advisory (pre-v1). Origin:
+Otto-168 naming-conflict BACKLOG row action step #3
+(naming-expert persona consultation on rename candidates).
+Author: Otto-170, applying `.claude/skills/naming-expert/`
+rubric + WebSearch trademark / product-space
+verification. **Advisory only**. Aaron Otto-168 explicit
+non-action: *"Do NOT unilaterally pick a name from Otto's
+candidate list. Aaron is the concept owner of the factory
+UI name."* This doc gives Aaron structured analysis, not
+a recommendation.
+
+## 1. What this doc is
+
+Per the Otto-168 BACKLOG row (at ~docs/BACKLOG.md:~4360),
+six rename candidates were proposed when the OpenAI
+Frontier naming conflict was first filed: **Zora,
+Starboard, Bridge, Horizon, Vantage, Aurora.** Otto-170
+applies the naming-expert discipline (denotation /
+connotation / boundary / searchability / longevity, plus
+domain-conflict scan) to each. This output is Aaron's
+decision aid, not the decision.
+
+## 2. Otto-169 scope confirmation on the motivating conflict


P1: This doc includes direct name attribution (e.g., "Aaron", "Otto-170", "Otto-168/169") in a forward-looking docs/research artifact. docs/AGENT-BEST-PRACTICES.md explicitly says "No name attribution in code, docs, or skills"—use role references (e.g., "human maintainer", "naming analysis agent") and put named attribution only in memory/persona/** (and optionally docs/BACKLOG.md). Please rewrite the intro and other occurrences to follow that rule.

Suggested change

# Frontier UI Rename — Candidate Analysis (Otto-170)

**Status:** research-grade advisory (pre-v1). Origin:

Otto-168 naming-conflict BACKLOG row action step #3

(naming-expert persona consultation on rename candidates).

Author: Otto-170, applying `.claude/skills/naming-expert/`

rubric + WebSearch trademark / product-space

verification. **Advisory only**. Aaron Otto-168 explicit

non-action: *"Do NOT unilaterally pick a name from Otto's

candidate list. Aaron is the concept owner of the factory

UI name."* This doc gives Aaron structured analysis, not

a recommendation.

## 1. What this doc is

Per the Otto-168 BACKLOG row (at ~docs/BACKLOG.md:~4360),

six rename candidates were proposed when the OpenAI

Frontier naming conflict was first filed: **Zora,

Starboard, Bridge, Horizon, Vantage, Aurora.** Otto-170

applies the naming-expert discipline (denotation /

connotation / boundary / searchability / longevity, plus

domain-conflict scan) to each. This output is Aaron's

decision aid, not the decision.

## 2. Otto-169 scope confirmation on the motivating conflict

# Frontier UI Rename — Candidate Analysis

**Status:** research-grade advisory (pre-v1). Origin:

prior naming-conflict BACKLOG action step #3

(naming-expert persona consultation on rename candidates).

Prepared using the `.claude/skills/naming-expert/`

rubric plus WebSearch trademark / product-space

verification. **Advisory only**. Prior guidance from the

human maintainer was explicit: *"Do NOT unilaterally pick a

name from the candidate list. The human maintainer is the

concept owner of the factory UI name."* This doc gives the

human maintainer structured analysis, not a recommendation.

## 1. What this doc is

Per the prior BACKLOG row (at ~docs/BACKLOG.md:~4360),

six rename candidates were proposed when the OpenAI

Frontier naming conflict was first filed: **Zora,

Starboard, Bridge, Horizon, Vantage, Aurora.** This

analysis applies the naming-expert discipline

(denotation / connotation / boundary / searchability /

longevity, plus domain-conflict scan) to each. This

output is a decision aid for the human maintainer, not

the decision.

## 2. Prior scope confirmation on the motivating conflict

Copilot · 2026-04-24T09:48:06Z

+Per the Otto-168 BACKLOG row (at ~docs/BACKLOG.md:~4360),
+six rename candidates were proposed when the OpenAI
+Frontier naming conflict was first filed: **Zora,
+Starboard, Bridge, Horizon, Vantage, Aurora.** Otto-170
+applies the naming-expert discipline (denotation /
+connotation / boundary / searchability / longevity, plus
+domain-conflict scan) to each. This output is Aaron's
+decision aid, not the decision.


P1: The BACKLOG cross-reference appears incorrect. This doc points to docs/BACKLOG.md:~4360 as the Otto-168 rename-candidate row, but line ~4360 in docs/BACKLOG.md is a "Frontier plugin inventory" entry and does not mention rename candidates or "Otto-168". Please update the citation to the correct BACKLOG row/line (or remove the line-number claim and link to the actual row text).

Suggested change

Per the Otto-168 BACKLOG row (at ~docs/BACKLOG.md:~4360),

six rename candidates were proposed when the OpenAI

Frontier naming conflict was first filed: **Zora,

Starboard, Bridge, Horizon, Vantage, Aurora.** Otto-170

applies the naming-expert discipline (denotation /

connotation / boundary / searchability / longevity, plus

domain-conflict scan) to each. This output is Aaron's

decision aid, not the decision.

Per the Otto-168 BACKLOG row documenting the initial

rename-candidate list, six rename candidates were

proposed when the OpenAI Frontier naming conflict was

first filed: **Zora, Starboard, Bridge, Horizon,

Vantage, Aurora.** Otto-170 applies the naming-expert

discipline (denotation / connotation / boundary /

searchability / longevity, plus domain-conflict scan) to

each. This output is Aaron's decision aid, not the

decision.

Copilot · 2026-04-24T09:48:06Z

+- `docs/research/frontier-ux-zora-evolution-2026-04-24
+  .md` — primary rename target (currently uses Zora
+  in filename; this analysis flags Zora as NOT VIABLE).


P2: The cross-reference to the UX doc has a hard line-break inside the filename (frontier-ux-zora-evolution-2026-04-24 then .md). This breaks copy/paste and may prevent Markdown auto-linking. Keep the path on one line with no extra whitespace.

Suggested change

- `docs/research/frontier-ux-zora-evolution-2026-04-24

.md` — primary rename target (currently uses Zora

in filename; this analysis flags Zora as NOT VIABLE).

- `docs/research/frontier-ux-zora-evolution-2026-04-24.md`

— primary rename target (currently uses Zora in

filename; this analysis flags Zora as NOT VIABLE).

Copilot · 2026-04-24T09:48:07Z

+  `docs/definitions/KSK.md`). **Aurora is the governance
+  / alignment architecture name**, not the UI layer.


P1: docs/definitions/KSK.md is referenced as an existing doc, but docs/definitions/ does not exist in the repo right now (so the link is currently dead). Either point to the current source of truth for the Aurora/Zeta/KSK naming triangle, or explicitly mark this as a planned doc and link to the BACKLOG item that will create it.

Suggested change

`docs/definitions/KSK.md`). **Aurora is the governance

/ alignment architecture name**, not the UI layer.

tracked in the Otto-168 naming-conflict BACKLOG row).

`docs/definitions/KSK.md` is a planned definitions doc,

not a file that exists in the tree today. **Aurora is

the governance / alignment architecture name**, not the

UI layer.

Copilot · 2026-04-24T09:48:07Z

+- Otto-168 memory pointer (MEMORY.md top entry for
+  macOS-declined + Frontier-naming-conflict context).


P1: The cross-reference "MEMORY.md top entry" appears to use the wrong path. The repository has memory/MEMORY.md (not a root-level MEMORY.md), so this reference is currently broken/misleading. Please update the path accordingly.

Suggested change

- Otto-168 memory pointer (MEMORY.md top entry for

macOS-declined + Frontier-naming-conflict context).

- Otto-168 memory pointer (`memory/MEMORY.md` top entry

for macOS-declined + Frontier-naming-conflict context).

Copilot · 2026-04-24T09:48:07Z

+| Candidate | Agentic-AI conflict | Trademark risk | Distinctiveness | Verdict |
+|-----------|---------------------|----------------|-----------------|---------|
+| Zora      | Deloitte Zora AI    | ACTIVE LITIGATION | Medium | NOT VIABLE |
+| Starboard | None                | Low             | High            | VIABLE |
+| Bridge    | None                | Low             | Very low        | NOT RECOMMENDED |
+| Horizon   | Topia + Eagleview   | High (crowded)  | Low             | NOT VIABLE |
+| Vantage   | Palantir Vantage    | High            | Medium          | NOT RECOMMENDED |
+| Aurora    | Factory internal + AWS/NEAR | High | Low | NOT VIABLE |


P2: The summary table uses leading double pipes (|| Candidate | ...), which adds an empty first column in standard Markdown table rendering. If the intent is a normal 5-column table, change these to single leading pipes (| Candidate | ...) on the header, separator, and rows.

Copilot AI review requested due to automatic review settings April 24, 2026 09:44

AceHack enabled auto-merge (squash) April 24, 2026 09:44

Copilot started reviewing on behalf of AceHack April 24, 2026 09:44 View session

AceHack merged commit aa6acbd into main Apr 24, 2026
12 checks passed

AceHack deleted the docs/frontier-rename-analysis-otto-170 branch April 24, 2026 09:46

Copilot AI reviewed Apr 24, 2026

View reviewed changes

Copilot AI mentioned this pull request May 9, 2026

docs(B-0168): regulator-response worked translations — 5th content-shape slice #2232

Merged

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs: Frontier rename candidate analysis — advisory (Otto-170)#349

docs: Frontier rename candidate analysis — advisory (Otto-170)#349
AceHack merged 1 commit into
mainfrom
docs/frontier-rename-analysis-otto-170

AceHack commented Apr 24, 2026

Uh oh!

chatgpt-codex-connector Bot commented Apr 24, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		`docs/definitions/KSK.md`). **Aurora is the governance
		/ alignment architecture name**, not the UI layer.

-  `docs/definitions/KSK.md`). **Aurora is the governance
-  / alignment architecture name**, not the UI layer.
+  tracked in the Otto-168 naming-conflict BACKLOG row).
+  `docs/definitions/KSK.md` is a planned definitions doc,
+  not a file that exists in the tree today. **Aurora is
+  the governance / alignment architecture name**, not the
+  UI layer.

		- Otto-168 memory pointer (MEMORY.md top entry for
		macOS-declined + Frontier-naming-conflict context).

Conversation

AceHack commented Apr 24, 2026

Summary

Verdict table

Key finding

Starboard analysis

Non-actions

Test plan

Uh oh!

chatgpt-codex-connector Bot commented Apr 24, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants