FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Adding a Narrative Director and a shared content-production foundation
Bringing a dedicated structure-and-writing role, nine templates, and a pre-design Narrative gate into one operating model
Purpose
Building Wiroh's corporate site required a role that could handle brand and story structure together with articles, scripts, site copy, calls to action, and presentation wording without splitting those responsibilities across separate owners. The organization already had roles for requirements, design, technical design, implementation, legal work, and review, but no dedicated role continuously owned both Narrative structure and written outputs.
The work also needed a shared production foundation that kept creative expression from overriding actual decisions or product facts. It aimed to separate confirmed facts, approved claims, creative hypotheses, dramatization, placeholders, and private inputs, then make the same version of the Narrative reviewable before design began.
Implementation
.codex/agents/narrative-director.toml added Narrative Director + Writer as one dedicated role. It owned brand and story architecture, message hierarchy, continuity, writing for articles, scripts, site copy and calls to action, and deck storylines as an integrated scope. Brand truth and organization governance, product facts, visual design, technical design, implementation, legal judgment, and independent review remained with their existing owners. The role was defined as a peer specialist launched directly by the central lifecycle owner rather than as a child of a domain lead.
.agents/skills/narrative-development/SKILL.md defined a shared workflow for Brand Bibles, Story Worlds, AI employee characters, series, seasons, episodes, articles, scripts, site copy, calls to action, and deck storylines. Before writing, it required a linked Task, the Narrative source of truth, the relevant template, and the review checklist. It treated the truth owner, product facts, and legal judgment as separate inputs. When required inputs or publication boundaries were missing, the workflow returned the gap instead of inventing an answer.
- Define the audience, desired outcome, channel, public boundary, and source facts first.
- Build the message hierarchy from Why, Belief, What, Current chapter, and Promise.
- Separate confirmed facts, approved claims, creative hypotheses, dramatization, placeholders, and private or prohibited inputs.
- Create a content brief and message map that every role can reuse before expanding an approved brief into individual pieces of writing.
- Check truthfulness, continuity, audience fit, internationalization, and public boundaries, and do not report completion before receiving explicit confirmation.
organization-level Narrative source of truth became the organization-level entry point for the Narrative source of truth and defined ownership, artifact status, and the change flow. The same area added nine templates—Brand Bible, Story World, AI Employee Profile, Series Bible, Season Outline, Episode Brief, Corporate Site Narrative, Shared Content Brief, and Deck Outline—plus a checklist covering truth and boundaries, Narrative and messaging, and shared inputs and delivery. These templates were scaffolds for creating later artifacts with a consistent information structure, not completed Narrative artifacts.
When design depended on Narrative output, the operating sequence required the dedicated role to create a versioned artifact, obtain explicit confirmation for that same version, align it with brand truth and governance, receive CEO confirmation, and record the passed gate before starting the design role. A content change after confirmation required the changed version to be checked again before the gate could pass. This sequence was synchronized across AGENTS.md, .agents/skills/software-delivery/SKILL.md, operating model, and handoff examples.
The first cross-document check found two blockers: legacy ownership and design start conditions contradicted the new role contract, and the Narrative gate was missing from the gate lists in the operating documentation and delivery Skill. Ownership and start conditions were consolidated into one active sequence, the missing gate was synchronized, and a second check confirmed that the contradictions had been removed.
Verification parsed the project configuration and eight agent definitions as TOML and checked unique role IDs, consistency of thread capacity and depth, Skill frontmatter, the UI-metadata YAML, routing, hierarchy, source-of-truth references, stale role counts and start conditions, and whitespace errors in the diff. The official quick validator could not start because its YAML package was unavailable in the environment, so YAML and frontmatter syntax were checked with another standard parser.
The following excerpt from .agents/skills/narrative-development/SKILL.md was checked line by line against the primary Commit diff at the cutoff.
## Before Writing
1. `AGENTS.md` とlinked Task Issueを確認する。Taskがなければsubstantive artifactを開始しない
2. approved narrative source を読む
3. 対象に合うthe matching narrative template and review checklistを使う
4. Yuiが所有するbrand truth、Ryomaが所有するproduct facts / value / roadmap、Yasuが所有するlegal judgmentを入力として分離する
5. fact、approved claim、creative hypothesis、dramatization、placeholder、private / prohibited inputを分類する
6. 自分がdomain leadのchildではなく、Makoが直接起動するspecialistであることを確認する。structured handoffにscope、inputs、dependencies、acceptance、expected outputs、開始・合流・停止条件、返却先がなければ不足を返すRendering diagram…
What was confirmed
Verification results
The shared production foundation contained a dedicated role that kept Narrative structure and writing together, the Narrative Development Skill, an organization-level source of truth, nine templates, and a review checklist.
The path from a Narrative artifact to design required confirmation of the same version, alignment with brand truth and governance, CEO confirmation, and a recorded gate. The operating rules, delivery Skill, and reader-facing documentation also agreed that a content change required another review.
The two blockers found during the first check—ownership and start-condition conflicts, and incomplete gate synchronization—were corrected. The second check found no remaining severity-rated inconsistencies, and the TOML, YAML, frontmatter, role-inventory, routing, stale-reference, and diff checks passed.
The official quick validator itself was not run because its YAML package was unavailable; syntax was checked with another parser instead. The completed scope at this point was the production foundation. Actual Narrative artifacts such as the Brand Bible and Story World, downstream design, and implementation had not yet been created or completed.
Basis for completion
The shared content-production foundation was considered complete when the dedicated role's responsibilities and boundaries, the Skill's triggers and workflow, the source of truth, templates, review checklist, and pre-design Narrative gate had been applied as one operating model, and the final structure passed static and cross-document checks after the initial contradictions were corrected.