FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Separating technical documentation from AI operating rules
Moving development, deployment, and scope into a project guide and three documents while removing child-specific agent artifacts
Purpose
The Wiroh corporate site kept site-specific technical information and organization and agent governance owned by the parent workspace in the same child-local instruction file. The organizational source of truth needed to move to the parent while technical information remained readable within the child repository.
Although the parent workspace and child repository occupied one directory tree, they maintained separate Git branches, working trees, commits, and remotes. The entry documentation needed to explain where to start Codex, where to read technical information, and from which repository root to inspect state.
Implementation
project guide became the repository entry point. It identified the static Wiroh corporate site, its Astro, TypeScript, and pnpm stack, its placement below the parent workspace, the requirement to use the parent workspace root for Codex, and the need to inspect parent and child Git state separately. It retained a concise command table and linked to purpose-specific documentation for details.
Technical information was separated into three repository-root-relative files. development guide owned the development baseline and local workflow, deployment guide owned static delivery and publication boundaries, and site scope guide owned the initial included and excluded capabilities.
- development guide: Astro, TypeScript, pnpm, and Node.js baselines; install, development, check, build, and preview commands; dependency policy; directory boundaries; CSS; and quality checks.
- deployment guide: Cloudflare Pages build and output settings, the canonical domain, headers, robots and sitemap behavior, public environment values, secrets, and responsibility boundaries for external publication operations.
- site scope guide: routes included in the initial static site, capabilities kept in separate repositories, initially excluded CMS, blog, server endpoint, and authentication work, plus legal, design, and publication prerequisites.
Versions, commands, and delivery settings in the documentation were checked against package settings, site build settings, workspace settings, the CI workflow, the environment-setting template, public-header settings, crawler settings, and the explanatory-comment policy. The reader-facing documentation recorded the static-site implementation as it existed at the cutoff rather than defining an unimplemented target.
After the technical information was moved, the child-local AI operating source of truth was deleted. The first review failed after finding a hidden Issue template that still required the deleted instruction file and repeated internal role routing. AI-work template was then deleted as well, aligning the child with the boundary that organization and agent governance was not duplicated there.
Verification searched the tracked tree, including hidden files, for AI operating source of truth, legacy instruction artifact, legacy instruction artifact, references to the removed instructions, and remaining role routing. It also checked the diff for whitespace errors and ran pnpm check and pnpm build.
The primary diff was checked line by line to confirm that the behavior described above matched the change at the cutoff.
# Wiroh Corporate Site Agent Guide
このファイルは、Codex がchild repositoryで作業するための child-local 指示書です。reader-facing guideは人間向けの概要、AGENTS.md は agent 向けの作業規約として扱います。Rendering diagram…
What was confirmed
Verification results
The workspace entry, development baseline, deployment settings, and initial site scope became navigable by purpose through project guide and three technical documents. The documentation also established the parent workspace as the Codex entry point while requiring separate Git inspection for parent and child.
The child-local AI operating source of truth and the old AI-agent Task template were removed. Searches of the corrected tracked tree found no AI operating source of truth, legacy instruction artifact, legacy instruction artifact, stale instruction-file references, or role routing duplicated into the child.
pnpm check completed with zero errors, warnings, or hints, and pnpm build generated five static pages and a sitemap. CI and preview checks for the same change also passed.
After the hidden artifact found during the first check was removed, another search of the tracked tree and hidden files confirmed that the deletion targets and stale references no longer remained.
The Activity did not change or verify the production Cloudflare account, DNS, custom domain, or production publication. It also did not runtime-test the Codex instruction chain when opening only the child repository as a workspace.
Basis for completion
The Activity was complete when site-specific technical information had been separated into the project guide and three documents, child-side organization and agent governance artifacts had been removed, and the corrected change had passed static searches, checks, build, CI, and preview.