Repository navigation
feat(marketing): an unnamed speaker is written in the third person - #77
Merged
Merged
Conversation
When the material is somebody speaking (an interview, a recorded talk, a KS
session) and nothing says who they are, the writing skills had no rule for it.
Measured in orbitant-employents on 2026-09-15 (ADR-026): the same interview
transcript with a line naming the interviewee came out as a third-party case
study; without it, it came out in the first person ("mi equipo", "nuestro
almacén"), telling another company's story as Orbitant's.
Mercuria is about to stop holding the draft until somebody names the speaker:
it will write first and ask at the end, then place the name with exact
substitutions and never rewrite the piece. That only works if the piece has a
place for the name. On a third-person draft ("la persona entrevistada") it
worked on the proxies measured; on a first-person one there was nowhere to put
it.
So the rule goes where ADR-020 says writing rules live, in the brain:
- blog-post-create: a subsection under Input. Third person for everything the
speaker lived, one neutral phrase used the same way throughout ("la persona
entrevistada", "la persona que da la charla"), no invented name, role,
gender or company, and neither the signer nor the institutional "nosotros"
takes their story.
- x-thread, x-post: the same rule beside "Somebody else's words", in English
by default.
- linkedin-post: the same rule in Input, for a source that rests on an
unnamed speaker.
- yt-description: the speaker line uses the neutral phrase instead of a name
nobody gave.
Talks are covered as well as interviews, since a recorded session reaches the
same path.
MINOR, because five skills behave differently for an unnamed speaker. Everything moves together, as validate-versions.cjs and this repo's precedent require: plugin.json, marketplace.json, README's table and install line, .claude/CLAUDE.md's tree and Current State table, the meta package (1.4.0 -> 1.5.0), and each changed skill's own frontmatter.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What happened
In orbitant-employents, Mercuria holds the draft until somebody names whoever speaks in an interview or talk (ADR-026). The owner ruled (2026-09-26, reconfirmed 2026-10-08) that the ask must not block: write first, ask once at the end, then place the name with exact substitutions and never rewrite the piece.
That work was parked (weorbitant/orbitant-employents#137) for one measured reason: with nobody named, Sonnet writes the speaker's story in the first person ("mi equipo", "nuestro almacén", ADR-026, 2026-09-15), and then a name has nowhere to go. On a third-person draft ("la persona entrevistada…") placing the name worked. How to write about somebody not named yet is a writing rule, so under ADR-020 it belongs here, not in the harness.
What changes
Talks are covered as well as interviews: a recorded Knowledge Sharing reaches the same path.
Measured
Measured from orbitant-employents (weorbitant/orbitant-employents#269) with this branch's built package swapped into
node_moduleslocally (nothing published, no pin changed), Sonnet as the writer, fiveblog-post-createdrafts from an unnamed interview (x3) and talk (x2):Not measured: linkedin-post, x-thread, x-post and yt-description outputs.
Checks
npm run checkgreen (lint, validate, tests, package build:@orbitant/brain-marketing@1.10.0,@orbitant/brain@1.5.0).Not merged and not published: a release tag is needed before the employents PR can pin 1.10.0.