mirror of
https://github.com/merlinhu1/codex-game-studio.git
synced 2026-08-25 07:54:34 +02:00
chore: update truthmark to 2.2.6
This commit is contained in:
MerlinH
@@ -60,7 +60,12 @@ Treat the HTML comments under each template section as normative authoring guida
|
||||
Align existing docs to that template and write or repair section content so it satisfies the comment guidance while preserving accurate authored content.
|
||||
If the template is missing, use lane-specific sections: product truth says what must be true and why; engineering truth says how the repository currently realizes it.
|
||||
Teams may edit template files under the configured Truthmark templates root to define their local truth-doc standards.
|
||||
Prefer diff-friendly Markdown: one durable claim per bullet or line, paragraphs no longer than one or two short sentences, and bullets or tables for rules, criteria, fields, files, and lists.
|
||||
Truth-doc prose style:
|
||||
- Use professional, plain technical prose. Prefer specific current-state claims over promotional, symbolic, or generic significance language.
|
||||
- Avoid common AI-writing tells: pivotal, crucial, underscores, serves as, stands as, showcases, landscape, vague expert attributions, and generic upbeat conclusions.
|
||||
- Keep claims evidence-backed and diff-friendly: one durable claim per bullet or line; paragraphs should be no longer than one or two short sentences.
|
||||
- Do not add personality, rhetorical flourish, first-person commentary, or marketing tone.
|
||||
- Rewrite dense or formulaic prose only when it improves readability without removing scope, evidence, decisions, or source references.
|
||||
Truth-doc shape repair review:
|
||||
- Truth Document may restructure only truth docs for the implemented behavior being documented.
|
||||
- repair shape in place only after the ownership review confirms the doc is the right bounded owner
|
||||
|
||||
@@ -32,6 +32,12 @@ Parent workflow:
|
||||
- No-update-needed rationale: why mapped truth is already current when no truth doc should change
|
||||
- Blockers: missing routing, ambiguous ownership, failed verification, unavailable evidence, or off-boundary write needs
|
||||
11. Only edit allowed truth docs/routes after Sync Intent is clear; if ownership is ambiguous, repair topology first when the repair is safe and in scope, otherwise stop and recommend Truth Structure instead of guessing.
|
||||
Truth-doc prose style:
|
||||
- Use professional, plain technical prose. Prefer specific current-state claims over promotional, symbolic, or generic significance language.
|
||||
- Avoid common AI-writing tells: pivotal, crucial, underscores, serves as, stands as, showcases, landscape, vague expert attributions, and generic upbeat conclusions.
|
||||
- Keep claims evidence-backed and diff-friendly: one durable claim per bullet or line; paragraphs should be no longer than one or two short sentences.
|
||||
- Do not add personality, rhetorical flourish, first-person commentary, or marketing tone.
|
||||
- Rewrite dense or formulaic prose only when it improves readability without removing scope, evidence, decisions, or source references.
|
||||
Topology review and repair:
|
||||
- before updating truth docs, verify the changed code resolves to a specific behavior-owned area and bounded truth owner
|
||||
- if routing is missing, stale, broad, overloaded, catch-all route only, or cannot map changed code to a bounded truth owner, run Truth Structure before syncing when topology repair is safe and in scope
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
status: active
|
||||
truth_kind: engineering-behavior
|
||||
last_reviewed: 2026-06-25
|
||||
last_reviewed: 2026-06-26
|
||||
---
|
||||
|
||||
# Approval Stores
|
||||
@@ -18,8 +18,6 @@ It covers canonical objective hashing, scope normalization, approval matching, e
|
||||
|
||||
It also covers reads, writes, and mutations. It does not own approval CLI syntax, runner/task eligibility, project initialization, or validation diagnostics.
|
||||
|
||||
This doc was created from the editable engineering-behavior template at docs/truthmark/templates/engineering-behavior.md.
|
||||
|
||||
## Current Implementation Behavior
|
||||
|
||||
- Approval stores are JSON objects.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
status: active
|
||||
truth_kind: engineering-behavior
|
||||
last_reviewed: 2026-06-25
|
||||
last_reviewed: 2026-06-26
|
||||
---
|
||||
|
||||
# Codex Roles And Workflows
|
||||
@@ -20,8 +20,6 @@ It also owns engine-reference prompt selection and generated workflow prompt con
|
||||
|
||||
It does not own process execution, task persistence, package installation, or generated project initialization side effects.
|
||||
|
||||
This doc was created from the editable engineering-behavior template at docs/truthmark/templates/engineering-behavior.md.
|
||||
|
||||
## Current Implementation Behavior
|
||||
|
||||
- Studio role IDs are canonical hyphenated strings.
|
||||
@@ -139,9 +137,9 @@ This doc was created from the editable engineering-behavior template at docs/tru
|
||||
## Engineering Decisions
|
||||
|
||||
- Decision (2026-05-28): Use Codex-native hyphenated role IDs as the user- and project-facing role contract.
|
||||
- Decision (2026-05-28): Keep workflow shortcuts render-only for this pass.
|
||||
- Decision (2026-05-28): Keep future planner, next, telemetry, ownership enforcement, hosted orchestration, background loops, and unbounded parallelism hidden.
|
||||
- Decision (2026-06-25): Allow explicit local task orchestration as a product-boundary feature area when implemented through bounded selected context, file-backed task state, run metadata, locks, approvals, validation, and docs.
|
||||
- Decision (2026-06-26): Workflow shortcut aliases render prompts and do not execute Codex.
|
||||
- Decision (2026-06-26): Keep planner/next, telemetry, ownership enforcement, hosted orchestration, background loops, and unbounded parallelism absent from role and workflow prompt surfaces.
|
||||
- Decision (2026-06-26): Keep local task orchestration ownership in runtime/task execution; role and workflow surfaces provide prompt and recipe inputs.
|
||||
- Decision (2026-06-13): Workflow prompts use the same context-contract renderer as role-run prompts.
|
||||
- Decision (2026-06-13): Workflow prompts include only selected workflow context.
|
||||
- Decision (2026-06-14): Add one specialist role ID per supported engine.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
status: active
|
||||
truth_kind: engineering-workflow
|
||||
last_reviewed: 2026-06-25
|
||||
last_reviewed: 2026-06-26
|
||||
---
|
||||
|
||||
# Runtime And Task Execution
|
||||
@@ -10,7 +10,7 @@ last_reviewed: 2026-06-25
|
||||
|
||||
Runtime and task execution connects prepared Codex Game Studio prompts to the Codex CLI.
|
||||
|
||||
It also preserves explicit task state and runs bounded verification, review, and fix loops. The product boundary now allows local, file-backed task orchestration when task state, locks, approvals, selected context, run metadata, and failures stay reviewable.
|
||||
It also preserves explicit task state and runs bounded verification, review, fix, and local task orchestration loops when task state, locks, approvals, selected context, run metadata, and failures stay reviewable.
|
||||
|
||||
## Scope
|
||||
|
||||
@@ -48,7 +48,7 @@ Runtime execution prepares bounded Codex prompts before side effects.
|
||||
|
||||
It evaluates studio write policy before mutation.
|
||||
|
||||
It records visible run and task state for non-inspection paths. It reports verification, review, and fix outcomes without hidden orchestration; future orchestration work must keep those outcomes explicit in `.codex/**` state.
|
||||
It records visible run, task, orchestration, verification, review, and fix outcomes in `.codex/**` state for non-inspection paths.
|
||||
|
||||
## Execution Model
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
status: active
|
||||
truth_kind: engineering-contract
|
||||
last_reviewed: 2026-06-25
|
||||
last_reviewed: 2026-06-26
|
||||
---
|
||||
|
||||
# CLI And Validation Contracts
|
||||
@@ -158,7 +158,7 @@ It does not own project scaffolding internals, role prompt content, or Codex run
|
||||
- Decision (2026-06-14): Validate engine reference packs by registered file presence and seed-review metadata shape.
|
||||
- Decision (2026-06-14): Validate active-engine materialized references without judging prose quality.
|
||||
- Decision (2026-06-17): Expose the expanded workflow catalog as render-only CLI shortcuts.
|
||||
- Decision (2026-06-17): Keep future planner, next, telemetry, hosted/background orchestration, unbounded parallelism, and ownership enforcement hidden.
|
||||
- Decision (2026-06-26): Keep planner/next, telemetry, hosted/background orchestration, unbounded parallelism, and ownership enforcement absent from public CLI and validation surfaces.
|
||||
- Decision (2026-06-25): Treat explicit local task orchestration as in-boundary once it has CLI behavior, validation, tests, and truth docs; keep hosted/background orchestration and unbounded parallelism hidden.
|
||||
- Decision (2026-06-17): Add local deterministic behavioral-evaluation subchecks.
|
||||
- Decision (2026-06-17): Do not use hosted evaluators, telemetry, hidden memory, or LLM judges for those checks.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
status: active
|
||||
truth_kind: engineering-behavior
|
||||
last_reviewed: 2026-06-25
|
||||
last_reviewed: 2026-06-26
|
||||
---
|
||||
|
||||
# Project Scaffolding
|
||||
@@ -20,8 +20,6 @@ It also owns generated project `AGENTS.md`, generated role prompts, and read-onl
|
||||
|
||||
It does not own Codex run execution, task lifecycle persistence, or repository-level CLI validation.
|
||||
|
||||
This doc was created from the editable engineering-behavior template at docs/truthmark/templates/engineering-behavior.md.
|
||||
|
||||
## Current Implementation Behavior
|
||||
|
||||
- `init` and `new` share the same initialization path.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
status: active
|
||||
truth_kind: engineering-workflow
|
||||
last_reviewed: 2026-06-25
|
||||
last_reviewed: 2026-06-26
|
||||
---
|
||||
|
||||
# Repository Bootstrap Routing
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
status: active
|
||||
truth_kind: engineering-behavior
|
||||
last_reviewed: 2026-06-25
|
||||
last_reviewed: 2026-06-26
|
||||
---
|
||||
|
||||
# Repository Overview
|
||||
@@ -32,7 +32,8 @@ They are listed in `docs/truthmark/routes/areas/repository.md`.
|
||||
- Role run commands render deterministic Codex prompts.
|
||||
- Unless in inspection mode, role run commands execute Codex with optional verification, review, and bounded fix passes.
|
||||
- Workflow shortcut commands are render-only prompt surfaces.
|
||||
- Workflow shortcuts do not imply hidden planner, hosted orchestration, background loops, unbounded parallelism, telemetry, or ownership enforcement behavior. Explicit local task orchestration is now allowed by the product boundary only when backed by reviewable `.codex/**` state.
|
||||
- Workflow shortcuts do not imply hidden planner, hosted orchestration, background loops, unbounded parallelism, telemetry, or ownership enforcement behavior.
|
||||
- Explicit local task orchestration is limited to reviewable `.codex/**` state.
|
||||
- Validation checks package metadata, source files, templates, role/workflow rendering, behavioral-evaluation scenarios, and customization packs.
|
||||
- It also checks future-surface guardrails, build output, and package install smoke behavior.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
status: active
|
||||
truth_kind: product-capability
|
||||
last_reviewed: 2026-06-25
|
||||
last_reviewed: 2026-06-26
|
||||
---
|
||||
|
||||
# Open Game Studio Codex-Native CLI
|
||||
@@ -95,12 +95,12 @@ Production templates are package-shipped assets selected by relevance.
|
||||
- 2026-06-13: Open Game Studio is a local-first Codex-native CLI/package for game-development repository workflows.
|
||||
- 2026-06-13: Open Game Studio is not a hosted studio service, daemon, general-purpose orchestrator, or game engine.
|
||||
- 2026-06-25: Explicit local task orchestration is inside the product boundary when it remains Codex-native, file-backed, bounded by selected context, policy-gated, and validated.
|
||||
- 2026-06-25: The first orchestration implementation is a foreground `task orchestrate` CLI with bounded concurrency, transient `.codex/locks/`, workflow task recipes, and no hosted/background/unbounded behavior.
|
||||
- 2026-06-26: Foreground task orchestration is exposed through `task orchestrate` with bounded concurrency, transient `.codex/locks/`, workflow task recipes, and no hosted/background/unbounded behavior.
|
||||
- 2026-06-13: Studio depth is optional and mode-controlled.
|
||||
- 2026-06-13: Lifecycle stage must remain separate from process strictness.
|
||||
- 2026-06-13: Generated project instruction contracts use `AGENTS.md` and `.codex/**`.
|
||||
- 2026-06-13: Generated project instruction contracts do not use `CODEX.md` or legacy compatibility shims.
|
||||
- 2026-06-13: Planner/next, telemetry, hard ownership enforcement, hosted/background orchestration, unbounded parallelism, and similar future-only surfaces remain absent until implemented, tested, and documented.
|
||||
- 2026-06-26: Planner/next, telemetry, hard ownership enforcement, hosted/background orchestration, unbounded parallelism, and similar surfaces remain out of scope unless a later product-boundary decision, implementation, tests, and truth docs bring them in.
|
||||
- 2026-06-13: Truthmark-backed docs guard repository truth in this checkout.
|
||||
- 2026-06-13: Truthmark workflow mechanics are not Open Game Studio product features.
|
||||
- 2026-06-17: Project-local customization is an extend-only, file-backed overlay for `custom-*` roles, workflows, and templates.
|
||||
|
||||
@@ -48,6 +48,16 @@ Separate rules from incidental implementation details; cite current implementati
|
||||
|
||||
{{core_rules}}
|
||||
|
||||
## Behavior Scenarios
|
||||
|
||||
<!--
|
||||
Use compact scenario blocks only where they clarify normal, fallback, or compatibility-critical behavior.
|
||||
Write scenarios as current truth, not desired requirements: `#### Scenario: <implemented case>` followed by `- **GIVEN** ...`, `- **WHEN** ...`, `- **THEN** ...`, and optional `- **AND** ...` bullets.
|
||||
Keep each bullet evidence-backed and observable; do not force a scenario for every rule.
|
||||
-->
|
||||
|
||||
{{behavior_scenarios}}
|
||||
|
||||
## Flows And States
|
||||
|
||||
<!--
|
||||
|
||||
Generated
+4
-4
@@ -17,7 +17,7 @@
|
||||
},
|
||||
"devDependencies": {
|
||||
"@types/node": "^24.13.2",
|
||||
"truthmark": "^2.2.5",
|
||||
"truthmark": "^2.2.6",
|
||||
"tsx": "^4.20.6",
|
||||
"typescript": "^5.9.3",
|
||||
"vitest": "^1.6.1"
|
||||
@@ -2530,9 +2530,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/truthmark": {
|
||||
"version": "2.2.5",
|
||||
"resolved": "https://registry.npmjs.org/truthmark/-/truthmark-2.2.5.tgz",
|
||||
"integrity": "sha512-Av2RJ+99FKYlJtDHLxVfth2aPbN0O+b8yT09ni2ojufrygTzzpeoeai+Fl8Jiubu7stSF+G7tO4SjpiHRE7jFQ==",
|
||||
"version": "2.2.6",
|
||||
"resolved": "https://registry.npmjs.org/truthmark/-/truthmark-2.2.6.tgz",
|
||||
"integrity": "sha512-b9GS/o3MtDSf1NutUsEIwIS2vWZp20xlBKBnOo3tWIDP69SkTtj9h/QCKZFuC5mDjLNxG7B44xO+kXbmv9RqCQ==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"dependencies": {
|
||||
|
||||
+1
-1
@@ -32,7 +32,7 @@
|
||||
},
|
||||
"devDependencies": {
|
||||
"@types/node": "^24.13.2",
|
||||
"truthmark": "^2.2.5",
|
||||
"truthmark": "^2.2.6",
|
||||
"tsx": "^4.20.6",
|
||||
"typescript": "^5.9.3",
|
||||
"vitest": "^1.6.1"
|
||||
|
||||
Reference in New Issue
Block a user