Promote approved CodexWriter governance and architecture to main - #13
Merged
Conversation
…templates, build report, Drive _LOG transcripts Adds the complete coherent fiction-agent scaffolding: - 11 SKILL.md files (fiction-orchestrator + 10 phase skills) - 4 JSON schemas (story-state, character-state, scene-state, continuity) - 4 templates (story bible, character dossier, scene, SKILL template) - Build report: docs/build-report-2026-08-26.md - Drive _LOG transcripts (ChatGPT 10:44pm + DeepSeek 04:09pm summaries) This is the post-build state ChatGPT-5 Sol should evaluate.
… basis) Records the finalized alignment evaluation and two approved framework decisions: - F1: JSON state model classified as provisional implementation prototype (not ratified) - F2: CodexWriter = reusable core with optional Dust & Ash profile Includes the four priority adjustments (tests/CI raised to High, portability reframed, framework vs. story approvals separated, source representation tempered) and the six-step immediate sequence. Public-log sensitivity inventory included (non-destructive): 3 _LOG transcript files identified as environment-specific session logs in the public branch. Recommendations presented for approval; no redaction/movement/deletion in this commit. Evaluation basis: commit 50dee18, 6 completed CodexWriter source analyses, independent inspection of Rhavekost at b7828700.
…ene) Per Option A of the public-log sensitivity inventory (docs/decisions/2026-08-26-alignment-evaluation.md), remove three CodexWriter session log transcripts from the public development branch. Sensitivity scan result: no credentials, tokens, PII, private URLs, or secrets found. Two hex strings appearing in scan results are commit-reference SHAs, not tokens, and match across all three files. Private copies preserved outside the Git repository at: /home/davehallmon/.codexwriter-private/logs/ Reusable conclusions incorporated into: - docs/decisions/2026-08-26-alignment-evaluation.md (Section 5 inventory + Section 6 task list) These were process records, not durable documentation. No history rewrite required.
…ene) Per Option A of the public-log sensitivity inventory (docs/decisions/2026-08-26-alignment-evaluation.md), remove three CodexWriter session log transcripts from the public development branch and update all references to them. Files removed: - docs/source-analysis/codexwriter_log_chatgpt_1044pm_full.md - docs/source-analysis/codexwriter_log_chatgpt_1044pm_summary.md - docs/source-analysis/codexwriter_log_deepseek_0409pm_summary.md References updated: - docs/build-report-2026-08-26.md (download list and Drive _LOG downloads table; total size corrected) - docs/decisions/2026-08-26-alignment-evaluation.md (inventory table + post-cleanup note) Files modified in this commit: 2 (build-report, alignment-evaluation) Files removed from tree: 3 (the log transcripts) Files unchanged: all source analyses, schemas, skills, templates, architecture docs Private copies preserved outside the repository at: /home/davehallmon/.codexwriter-private/logs/ Scan result: no credentials, tokens, PII, private URLs, or secrets found. Two hex strings appearing in scan results are public commit-reference SHAs, not tokens. No history rewrite required. No Rhavekost analysis begun. No framework or implementation changes included.
Draft source analysis of rhavekost/author-toolkit pinned at upstream commit b78287003edf52e5f0784ee2b4a00411173358f. Key findings for CodexWriter: - Reader testing runs as context-isolated pass with explicit stopping (contradicts current CodexWriter reader-simulation design) - Prose audits diagnose, stop, wait for author disposition, then apply approved fixes (contradicts current CodexWriter prose-editing design) - Story Bible as persistent state across sessions + session-end notes - 5 editorial personas: Developmental Editor, Line Editor, Character Consultant, Continuity Tracker, Brainstorm Partner - Vendored avoid-ai-writing (MIT, Conor Bronsdon) with preserved upstream LICENSE; ATTRIBUTION.md missing at pin (provenance gap) - Platform: Claude Code plugin only; no CLI, no cross-host support - No structured state model, no deterministic validator, no CI/tests Pending verification: actual SKILL.md contents at b7828700 were not fully read; ChatGPT-5 Sol line-range quotes consistent with README but should be verified by direct reading before CodexWriter relies on specific mechanics. No architecture or crosswalk decision in this commit. Isolated on development until reviewed and approved.
…828700" This reverts commit 1aaa41e.
… directly-read primary sources Rebuilt from Git clone at pinned commit b78287003edf52e5f0784ee2b4a00411173358f. All quotations are from directly-read primary sources; no secondhand ChatGPT quotations used as evidence. Corrections applied: - SHA corrected: b78287003edf52e5f0784ee2b4a004111173358f (40 chars) - ATTRIBUTION.md verified present and fully read (945 bytes) — draft false claim of 404 removed - finding-schema.json verified present and fully analyzed (902 bytes) — draft claim of unread removed - All six SKILL.md files directly read: fiction-workshop, prose-mechanics, story-structure, narrative-nonfiction, character-archetypes, avoid-ai-writing - All fiction-workshop references directly read (9 files) - All character-archetypes references directly read (6 files) - All narrative-nonfiction references directly read (7 files) - prose-mechanics SKILL.md, sentence-length-variance, cliches-audit, audit-tracker-template directly read - 79-file tracked tree inventory at pinned commit included - Branch isolation: committed only to source-analysis/rhavekost, not development@c8b04aa Status: Ready for review — not yet accepted. No seven-source synthesis begun. development@c8b04aa untouched.
…ME status Corrections to the rebuilt rhavekost analysis (7ffa8d2): - Fixed category counts in §1 to match actual pinned-tree inventory - Reconciled §1 (observed) with §11 (unverified) so they describe the same inspection scope - Added story-structure references and artifact templates to the inspected-files ledger (directly read in this pass) - Updated README.md status: Not started → Ready for review at b78287003edf52e5f0784ee2b4a00411173358f - Removed avoid-ai-writing partial-read contradiction; noted it was read in part with specific gaps to verify Verified: development@c8b04aa untouched.
…audit taxonomy, defer detection rules
Accept the Rhavekost analysis at 7348178. §11 limitations retained as non-blocking follow-ups. Update source-analysis README: rhavekost status → Merged analysis complete. Next step: seven-source synthesis and state-architecture review (separately authorized). No synthesis performed in this merge.
Merge the accepted documentation state at c4de9df into a clean branch from development@0e999a9. This branch contains exactly six files: - ARCHITECTURE.md - docs/architecture/seven-source-synthesis-2026-08-27.md - docs/architecture/seven-source-synthesis-ratification-addendum.md - docs/crosswalk.md - docs/decisions/2026-08-26-alignment-evaluation.md - docs/source-analysis/README.md Source: c4de9df (accepted documentation tree). Base: development@0e999a9392683878a8cca9b1760cf92c81176c85. No PROGRESS.md included. No other files modified.
Ratified-requirement traceability, schema-by-schema impact matrix, skill-by-skill impact matrix, template-by-template impact matrix, new artifact candidates, dependency sequence, minimal vertical slice, testing and evidence plan, licensing and provenance impact, and a numbered decision register for Dave. Planning and analysis only — no implementation, schema change, skill change, template change, validator, test, CI, dependency installation, or Dust & Ash extraction authorized by this commit.
Add canonical JSON roadmap, task, decision, environment, and run data; generate root PROGRESS, STATUS, ROADMAP, and ENVIRONMENT views deterministically; and enforce freshness with tests, CI, and CODEOWNERS routing. Source state remains explicit to avoid impossible self-referential commit hashes. Branch-protection settings remain a repository-owner configuration step.
Approved by repository owner. Includes accepted architecture integration, planning lineage, deterministic operational views, tests, CI, and ownership controls.
Preserve main history while resolving the independently added ENVIRONMENT.md in favor of the approved generated view backed by project/control/environment.json. No other main-only paths differ.
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
2 participants
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.
Repository-owner approved promotion of the accepted architecture integration, schema and skill prototype, planning record, and deterministic operational-control setup from development to main. The Governance Views workflow passed on the governance head before integration into development. This PR intentionally replaces the separately uploaded main-branch ENVIRONMENT.md with the generated, human-owned environment view backed by project/control/environment.json.