Skip to content

docs(positioning): user-docs 'What is Trinity' leads with the operating-system line (abilityai/trinity-enterprise#798) - #3257

Merged
vybe merged 1 commit into
devfrom
feature/798-positioning-docs-source
Oct 6, 2026
Merged

vybe merged 1 commit into
devfrom
feature/798-positioning-docs-source

Conversation

@vybe

@vybe vybe commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Fixes abilityai/trinity-enterprise#798 — the docs-source half of the ADR-0011 positioning epic (abilityai/trinity-enterprise#796). Independent branch off dev — the four #796 children touch disjoint files and merge in any order (operator, 2026-10-05). Draft until the chain is in.

What

  • docs/user-docs/getting-started/overview.md — the "What is Trinity" lead now opens with the operating-system line and its paired promise; the second sentence keeps the page's existing concrete description ("Concretely, it is infrastructure for deploying, orchestrating, and governing fleets of autonomous AI agents on your own hardware.").
  • docs/user-docs/faq/getting-started.md — the "What is Trinity?" answer leads the same way; the rest of the answer is unchanged.
  • Two lines, two files, nothing else. Both openings match the wording of trinity-docs PR Feature/gemini runtime support #2 for the same answers, so the next docs-site sync carries that text instead of reverting it.

Rulings carried (orchestrator, on the operator's behalf — plan file)

  1. Overview second sentence: the plan's "Concretely, it is infrastructure for…" line — keeps existing content, adds no new claim; "sovereign" / "model-agnostic" stay out of the lead.
  2. No edits outside the two lines (FAQ lines 19/88/92 state facts, not what Trinity is).
  3. The four same-phrase hits in CLAUDE.md, docs/memory/architecture.md, docs/memory/requirements/overview.md and docs/diagrams/01-system-overview.md are rows of sibling abilityai/trinity-enterprise#800 (branch feature/800-positioning-engineer-context) — untouched here.
  4. Vertex sync waits on the next release cut (sync-docs-to-vertex.yml runs on main only) — see Before merge.
  5. Both wordings ship exactly as trinity-docs PR Feature/gemini runtime support #2 wrote them ("the compounding intelligence it builds is yours" in the overview, "compounding intelligence your company owns" in the FAQ); the variance is an FYI to the docs owner, not changed here.
  • The literal ** in the overview lead reaching ask_trinity through the Vertex sync matches other user-docs pages — accepted.

Review + security

/review (claude-fable-5-1, report-only): MERGEABLE — 0 critical, 0 informational. Both new lines byte-identical to the plan's After text; the issue's acceptance grep over docs/user-docs/getting-started/ docs/user-docs/faq/ docs/user-docs/README.md returns nothing (exit 1); none of the epic's banned phrases introduced; no test, workflow or script pins the old or new sentences; .claude, src/backend/enterprise and the root CLAUDE.md untouched; git merge-tree against live dev (493d2a6) clean. /cso --diff: 0 findings (PARTIAL by definition — no Docker on the review host; immaterial to a two-line copy change).

Tests

  • No unit test pins these files. The docs guards that run on docs/** were executed over the branch and stay green: enterprise-docs-guard pattern 0 hits, screenshot guard 0 errors, the two user-docs-scanning unit tests 43 passed (--noconftest, stdlib-only).
  • Not run here: the full unit island (CI).

Before merge

  • Merge to dev before or with trinity-docs PR Feature/gemini runtime support #2. If PR Feature/gemini runtime support #2 merges first, trinity-docs must not run a sync that touches faq/getting-started.md until this lands (DoD bullet 2; tracked on the sibling site issue).
  • After the next release cut to main: sync-docs-to-vertex green, then ask_trinity "what is Trinity?" answers with the new line (DoD bullet 3). No manual Vertex run before the release.
  • No open PR touches either file (checked 2026-10-05 22:42 UTC).

Handoffs

  • abilityai/trinity-enterprise#800 — the engineer-context / docs/memory hits (ruling 3).
  • trinity-docs owner (abilityai/trinity-enterprise#799) — FYI on the two slightly different promise wordings, both inherited verbatim from trinity-docs PR Feature/gemini runtime support #2.

🤖 Generated with Claude Code

…ine (abilityai/trinity-enterprise#798)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@trinity-ability trinity-ability left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merge-train: batch validated on train/20261006-1038 (#3270)

@vybe
vybe merged commit b5b8460 into dev Oct 6, 2026
23 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type-docs Documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants