FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Aligning Shiori's role as Narrative Designer
Applying a role rename that retains Writing and a relay contract that adds no interpretation to source messages
Purpose
Shiori's English role label was Narrative Director, but the addition of a Content Director responsible for creative-content production and distribution made the two Director titles harder to distinguish. The CEO wanted Shiori to become Narrative Designer, a specialist title that pairs naturally with UI/UX Designer.
Writing was not to be removed from Shiori's scope; it remained part of one continuous responsibility from Narrative Design through Writing. The goal was therefore to use Narrative Designer, which includes both design and authorship, rather than the compound label Narrative Designer & Writer.
During the work, the CEO also asked for the same scope to correct Mako's behavior of adding interpretations or information that were absent from source messages. The organizational configuration needed to define not only the role identity but also the boundary for relaying the words of the CEO and each role unchanged.
Implementation
Shiori's agent definition was renamed to .codex/agents/narrative-designer.toml, with name changed to narrative-designer and the English label changed to Narrative Designer. Self-identification, the invocation agent_type, and the description were aligned to the same identity while retaining the UI nickname shiori.
- Responsibility for designing and maintaining the Brand Bible, Story World, character continuity, message architecture, and storylines was retained.
- Responsibility for directly writing site copy, articles, dialogue, scripts, headlines, calls to action, and wording remained with the same role.
- Content Director remained the domain lead for creative-content production and distribution; its responsibilities were not exchanged with Narrative Designer.
- No role was added; one existing role was renamed.
Invocation contracts and references were updated together. AGENTS.md, the Narrative Development and Software Delivery Skills, related role definitions, execution rules, setup and operating guidance, the current Narrative source, and preserved material from two prior versions all moved from the former role id and label to the new identity. Historical content was not rewritten beyond synchronizing its owner identity reference.
The added Raw Relay Integrity rule limited relays to two layers: source payload and operational metadata. The source payload preserves the complete text sent by the CEO or a role without modification. Metadata contains only observable operating facts such as routing, role, lifecycle, status, approval waiting, and confirmation method.
- Mako cannot add requirements, background, constraints, hypotheses, plans, sequencing, design, summaries, supplements, or redesigns that are absent from the payload.
- Missing or ambiguous information remains unconfirmed instead of being filled by inference.
- A domain lead's decisions and plans are treated as that lead's own payload or handoff, never mixed into routing or lifecycle metadata.
The first relay example still contained an extra instruction authored by Mako, contradicting the new two-layer contract. The Organization Designer definition also used wording that could place domain-lead decisions in metadata. The extra instruction was removed, and the definition was corrected so domain-lead decisions belong to payload / handoff while metadata is reserved for routing and lifecycle facts.
Checks parsed all nine agent TOML files and verified filename-to-name alignment, role inventory, maximum concurrent threads, and depth. Searches across tracked artifacts then looked for the former narrative-director, the former Narrative Director, and the rejected Narrative Designer & Writer, while additional checks covered Skill frontmatter, the continuous Narrative Design-to-Writing responsibility, the Content Director boundary, Raw Relay Integrity prohibitions, and diff whitespace.
name = "narrative-designer"
description = "WirohのNarrative Designerとして、Narrative Designからsite copy、記事、セリフ、script、見出し、CTA等のWritingまで一気通貫で担うroleです。"Rendering diagram…
What was confirmed
Verification results
The change touched 36 files, adding 279 lines and removing 262. The agent filename, role id, English label, invocation contract, operating guidance, and Narrative sources aligned to one identity.
The inventory remained at nine agent definitions. All nine TOML files and their filename-to-name mappings passed, the maximum of 12 concurrent threads and depth of one remained unchanged, and no role was added.
The former narrative-director, former Narrative Director, and rejected Narrative Designer & Writer each had zero occurrences in tracked artifacts.
Shiori's continuous responsibility from Narrative Design through Writing and Content Director's boundary around creative-content production and distribution were preserved. Raw Relay Integrity also aligned on unchanged source payloads separated from operational metadata.
At the cutoff, the role rename and relay contract had been applied to the organization's current source. A runtime smoke test launching a new Shiori task and checking its self-identification was not performed by this Activity.
Basis for completion
The work was complete when Shiori's filename, role id, English label, invocation contract, and Narrative sources all aligned to Narrative Designer; former labels had zero occurrences while Writing responsibility and the Content Director boundary remained intact; and the two-layer contract for source payload and operational metadata was consistent.