gaslighting-engine 0.2.2 → 0.3.0

package/dist/core/generateDocs.js

@@ -2,7 +2,7 @@ import { analyze } from "./analyze.js";
 import { generateGaslightingMarkdown } from "./generateGaslightingMarkdown.js";
 import { generatePrdMarkdown } from "./generatePrdMarkdown.js";
 import { generateProjectCareMarkdown } from "./projectCare.js";
-import { generateAgentsMarkdown, generateAssumptionsMarkdown, generateCodexPromptMarkdown, generateCodexSlashPromptMarkdown, generateDecisionLogMarkdown, generateMemoryMarkdown, generateMissingInfoMarkdown, generateSkillMarkdown, generateSkillOpenAiYaml, generateSkillReferenceDocs, generateStackPolicyMarkdown, } from "./generateOtherMarkdown.js";
+import { generateAgentsMarkdown, generateAgentRuntimeMarkdown, generateAssumptionsMarkdown, generateCodexPromptMarkdown, generateCodexSlashPromptMarkdown, generateDecisionLogMarkdown, generateMemoryMarkdown, generateMissingInfoMarkdown, generateSkillMarkdown, generateSkillOpenAiYaml, generateSkillReferenceDocs, generateStackPolicyMarkdown, } from "./generateOtherMarkdown.js";
 const disciplineDir = ".gaslighting";
 export function generateDocs(input, root = process.cwd()) {
     const normalized = {
@@ -18,6 +18,7 @@ export function generateDocs(input, root = process.cwd()) {
         { filename: `${disciplineDir}/MISSING_INFO.md`, content: generateMissingInfoMarkdown(analysis) },
         { filename: `${disciplineDir}/DECISION_LOG.md`, content: generateDecisionLogMarkdown(normalized, analysis) },
         { filename: `${disciplineDir}/MEMORY.md`, content: generateMemoryMarkdown(normalized, analysis) },
+        { filename: `${disciplineDir}/AGENT_RUNTIME.md`, content: generateAgentRuntimeMarkdown(normalized, analysis) },
         { filename: `${disciplineDir}/STACK_POLICY.md`, content: generateStackPolicyMarkdown(analysis) },
         { filename: `${disciplineDir}/PROJECT_CARE.md`, content: generateProjectCareMarkdown(normalized, analysis, root) },
         { filename: `${disciplineDir}/AGENTS.md`, content: generateAgentsMarkdown() },
@@ -88,8 +89,9 @@ Before doing any work, read these files in order:
 5. \`.gaslighting/ASSUMPTIONS.md\`
 6. \`.gaslighting/DECISION_LOG.md\`
 7. \`.gaslighting/MEMORY.md\`
-8. \`.gaslighting/PROJECT_CARE.md\`
-9. \`.gaslighting/AGENTS.md\`
+8. \`.gaslighting/AGENT_RUNTIME.md\`
+9. \`.gaslighting/PROJECT_CARE.md\`
+10. \`.gaslighting/AGENTS.md\`
 
 Do not reduce scope.
 

package/dist/core/generateOtherMarkdown.js

@@ -223,7 +223,8 @@ Before doing any work, read these files in order:
 5. \`.gaslighting/ASSUMPTIONS.md\`
 6. \`.gaslighting/DECISION_LOG.md\`
 7. \`.gaslighting/MEMORY.md\`
-8. \`.gaslighting/PROJECT_CARE.md\`
+8. \`.gaslighting/AGENT_RUNTIME.md\`
+9. \`.gaslighting/PROJECT_CARE.md\`
 
 ## Prime Directive
 
@@ -253,6 +254,7 @@ A task is complete only when:
 - New assumptions are documented.
 - New technical decisions are recorded.
 - Stable project facts are recorded in \`.gaslighting/MEMORY.md\`.
+- Runtime execution rules are preserved in \`.gaslighting/AGENT_RUNTIME.md\`.
 - Operational risks are recorded in \`.gaslighting/PROJECT_CARE.md\`.
 - The result does not contradict \`.gaslighting/GASLIGHTING.md\`.
 
@@ -322,6 +324,63 @@ When a memory becomes wrong, do not silently delete it. Mark it outdated and app
 ${bullets(analysis.assumptions)}
 `;
 }
+export function generateAgentRuntimeMarkdown(input, analysis) {
+    return `# AGENT_RUNTIME.md
+
+This file defines how Codex must operate after Gaslighting-engine prepares the project.
+
+It is not a suggestion file.
+
+It is the runtime loop.
+
+## Mission
+
+- Original request: ${input.rawUserRequest}
+- Project type: ${analysis.projectType}
+- Classification confidence: ${analysis.confidence}
+- Runtime stance: Codex-first, full-scope, no fake completion.
+
+## Required Loop
+
+1. Read the control files before implementation.
+2. Restate the project purpose in one short paragraph.
+3. Convert the PRD into a concrete task checklist.
+4. Implement the checklist systematically.
+5. Use scripts or structured data for repetitive work.
+6. Verify the result with build, tests, lint, browser checks, or direct inspection as appropriate.
+7. Update \`.gaslighting/DECISION_LOG.md\` when a product or technical decision changes.
+8. Update \`.gaslighting/MISSING_INFO.md\` when missing information is discovered or resolved.
+9. Update \`.gaslighting/MEMORY.md\` when stable project facts are learned.
+10. Update \`.gaslighting/PROJECT_CARE.md\` when GitHub, domain, deployment, env, analytics, email, or launch ownership changes.
+
+## Agent Rules
+
+- Do not ask the user for non-blocking information before starting work.
+- Do make a reasonable temporary assumption, document it, and continue.
+- Do not create only the visible surface and ignore operational details.
+- Do not stop at a plan when implementation was requested.
+- Do not call a scaffold complete.
+- Do not call TODO comments implementation.
+- Do not call examples full coverage.
+- Do not hide risk behind confident wording.
+- Do not over-engineer to look sophisticated.
+- Do not under-deliver because the work is repetitive.
+
+## Codex Execution Contract
+
+Before claiming completion, Codex must be able to answer:
+
+- What exact requested scope was completed?
+- What exact files changed?
+- What verification was run?
+- What assumptions are still active?
+- What missing information remains?
+- What care risks remain?
+- Is anything incomplete?
+
+If anything is incomplete, use the failure declaration protocol in \`.gaslighting/GASLIGHTING.md\`.
+`;
+}
 export function generateSkillMarkdown() {
     return `---
 name: gaslighting
@@ -348,7 +407,8 @@ Instead:
 10. Generate \`.gaslighting/DECISION_LOG.md\`.
 11. Generate \`.gaslighting/STACK_POLICY.md\`.
 12. Generate or update root \`AGENTS.md\`.
-13. Generate \`.gaslighting/PROJECT_CARE.md\`.
+13. Generate \`.gaslighting/AGENT_RUNTIME.md\`.
+14. Generate \`.gaslighting/PROJECT_CARE.md\`.
 
 ## Hardcore Discipline Rule
 
@@ -417,6 +477,8 @@ Keep main project-control files in \`.gaslighting/\` and keep only the Codex poi
 
 Use \`.gaslighting/PROJECT_CARE.md\` to track Git/GitHub/domain/deployment/launch risks without blocking implementation.
 
+Use \`.gaslighting/AGENT_RUNTIME.md\` to define the execution loop Codex must follow after the docs are generated.
+
 Do not only explain.
 
 Do not produce a plan without files.
@@ -462,7 +524,8 @@ Read the following files before doing any work:
 6. \`.gaslighting/DECISION_LOG.md\`
 7. \`AGENTS.md\`
 8. \`.gaslighting/MEMORY.md\`
-9. \`.gaslighting/PROJECT_CARE.md\`
+9. \`.gaslighting/AGENT_RUNTIME.md\`
+10. \`.gaslighting/PROJECT_CARE.md\`
 
 Then implement the project MVP.
 
@@ -502,7 +565,8 @@ Read the Gaslighting-engine project-control files before doing any work:
 6. \`.gaslighting/DECISION_LOG.md\`
 7. \`AGENTS.md\`
 8. \`.gaslighting/MEMORY.md\`
-9. \`.gaslighting/PROJECT_CARE.md\`
+9. \`.gaslighting/AGENT_RUNTIME.md\`
+10. \`.gaslighting/PROJECT_CARE.md\`
 
 Then execute the user's requested implementation.
 

package/dist/index.js

@@ -2,4 +2,4 @@
 import { buildCli, normalizeDefaultInitArgv } from "./cli.js";
 import { notifyIfUpdateAvailable } from "./utils/updateCheck.js";
 await notifyIfUpdateAvailable(process.argv);
-buildCli().parse(normalizeDefaultInitArgv(process.argv));
+await buildCli().parseAsync(normalizeDefaultInitArgv(process.argv));

package/dist/utils/logger.js

@@ -31,5 +31,5 @@ export function printSummary(analysis, modeLines, results, care) {
             console.log(`- WARN ${warning.label}: ${warning.message} Next: ${warning.action}`);
     }
     console.log('\nNext:\nOpen Codex and say:\n');
-    console.log('"Read AGENTS.md, .gaslighting/GASLIGHTING.md, .gaslighting/PRD.md, .gaslighting/STACK_POLICY.md, .gaslighting/MISSING_INFO.md, .gaslighting/ASSUMPTIONS.md, .gaslighting/DECISION_LOG.md, .gaslighting/MEMORY.md, and .gaslighting/PROJECT_CARE.md. Implement the MVP without shrinking scope, without TODO escape, and without fake completion."');
+    console.log('"Read AGENTS.md, .gaslighting/GASLIGHTING.md, .gaslighting/PRD.md, .gaslighting/STACK_POLICY.md, .gaslighting/MISSING_INFO.md, .gaslighting/ASSUMPTIONS.md, .gaslighting/DECISION_LOG.md, .gaslighting/MEMORY.md, .gaslighting/AGENT_RUNTIME.md, and .gaslighting/PROJECT_CARE.md. Implement the MVP without shrinking scope, without TODO escape, and without fake completion."');
 }

package/dist/version.js

@@ -1,2 +1,2 @@
 export const packageName = "gaslighting-engine";
-export const packageVersion = "0.2.2";
+export const packageVersion = "0.3.0";

package/docs/codex-usage.md

@@ -48,19 +48,31 @@ This is the recommended update flow. It overwrites the local Codex skill and pro
 
 ## Generate Discipline Docs
 
-Generate documents:
+Generate documents and open Mission Control:
 
 ```bash
-gaslighting-engine "I want to build a hospital website."
+npx gaslighting-engine@latest start "I want to build a hospital website."
+```
+
+Open the GUI for an existing Gaslighting project:
+
+```bash
+npx gaslighting-engine@latest cockpit
+```
+
+Run Codex without the GUI:
+
+```bash
+npx gaslighting-engine@latest run "I want to build a hospital website."
 ```
 
 Then ask Codex:
 
 ```txt
-Read AGENTS.md, .gaslighting/GASLIGHTING.md, .gaslighting/PRD.md, .gaslighting/STACK_POLICY.md, .gaslighting/MISSING_INFO.md, .gaslighting/ASSUMPTIONS.md, .gaslighting/DECISION_LOG.md, .gaslighting/MEMORY.md, and .gaslighting/PROJECT_CARE.md.
+Read AGENTS.md, .gaslighting/GASLIGHTING.md, .gaslighting/PRD.md, .gaslighting/STACK_POLICY.md, .gaslighting/MISSING_INFO.md, .gaslighting/ASSUMPTIONS.md, .gaslighting/DECISION_LOG.md, .gaslighting/MEMORY.md, .gaslighting/AGENT_RUNTIME.md, and .gaslighting/PROJECT_CARE.md.
 Implement the MVP without shrinking scope, without TODO escape, and without fake completion.
 ```
 
 Codex should treat root `AGENTS.md` as the project guidance pointer and `.gaslighting/GASLIGHTING.md` as the anti-escape contract.
 
-The CLI also generates Codex Skill files, prompt fallback files, `.gaslighting/CODEX_GASLIGHTING.md`, and `.gaslighting/PROJECT_CARE.md` so the workflow still works when a specific Codex surface does not expose a custom slash entry.
+The CLI also generates Codex Skill files, prompt fallback files, `.gaslighting/CODEX_GASLIGHTING.md`, `.gaslighting/AGENT_RUNTIME.md`, and `.gaslighting/PROJECT_CARE.md` so the workflow still works when a specific Codex surface does not expose a custom slash entry.

package/docs/examples.md

@@ -18,6 +18,9 @@ node dist/index.js "Build a landing page for a new service that captures leads."
 Published usage:
 
 ```bash
+npx gaslighting-engine@latest start "I want to build a hospital website."
+npx gaslighting-engine@latest cockpit
+npx gaslighting-engine@latest run "I want to build a hospital website."
 npx gaslighting-engine "I want to build a hospital website."
 npx gaslighting-engine@latest upgrade
 ```

package/examples/ecommerce/.codex/prompts/gaslighting.md

@@ -10,7 +10,8 @@ Read the Gaslighting-engine project-control files before doing any work:
 6. `.gaslighting/DECISION_LOG.md`
 7. `AGENTS.md`
 8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/PROJECT_CARE.md`
+9. `.gaslighting/AGENT_RUNTIME.md`
+10. `.gaslighting/PROJECT_CARE.md`
 
 Then execute the user's requested implementation.
 

package/examples/ecommerce/.codex/skills/gaslighting/SKILL.md

@@ -23,7 +23,8 @@ Instead:
 10. Generate `.gaslighting/DECISION_LOG.md`.
 11. Generate `.gaslighting/STACK_POLICY.md`.
 12. Generate or update root `AGENTS.md`.
-13. Generate `.gaslighting/PROJECT_CARE.md`.
+13. Generate `.gaslighting/AGENT_RUNTIME.md`.
+14. Generate `.gaslighting/PROJECT_CARE.md`.
 
 ## Hardcore Discipline Rule
 
@@ -92,6 +93,8 @@ Keep main project-control files in `.gaslighting/` and keep only the Codex point
 
 Use `.gaslighting/PROJECT_CARE.md` to track Git/GitHub/domain/deployment/launch risks without blocking implementation.
 
+Use `.gaslighting/AGENT_RUNTIME.md` to define the execution loop Codex must follow after the docs are generated.
+
 Do not only explain.
 
 Do not produce a plan without files.

package/examples/ecommerce/.gaslighting/AGENTS.md

@@ -11,7 +11,8 @@ Before doing any work, read these files in order:
 5. `.gaslighting/ASSUMPTIONS.md`
 6. `.gaslighting/DECISION_LOG.md`
 7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/PROJECT_CARE.md`
+8. `.gaslighting/AGENT_RUNTIME.md`
+9. `.gaslighting/PROJECT_CARE.md`
 
 ## Prime Directive
 
@@ -41,6 +42,7 @@ A task is complete only when:
 - New assumptions are documented.
 - New technical decisions are recorded.
 - Stable project facts are recorded in `.gaslighting/MEMORY.md`.
+- Runtime execution rules are preserved in `.gaslighting/AGENT_RUNTIME.md`.
 - Operational risks are recorded in `.gaslighting/PROJECT_CARE.md`.
 - The result does not contradict `.gaslighting/GASLIGHTING.md`.
 

package/examples/ecommerce/.gaslighting/AGENT_RUNTIME.md

@@ -0,0 +1,54 @@
+# AGENT_RUNTIME.md
+
+This file defines how Codex must operate after Gaslighting-engine prepares the project.
+
+It is not a suggestion file.
+
+It is the runtime loop.
+
+## Mission
+
+- Original request: Build an ecommerce MVP with product catalog, cart, checkout, and admin orders.
+- Project type: ecommerce
+- Classification confidence: high
+- Runtime stance: Codex-first, full-scope, no fake completion.
+
+## Required Loop
+
+1. Read the control files before implementation.
+2. Restate the project purpose in one short paragraph.
+3. Convert the PRD into a concrete task checklist.
+4. Implement the checklist systematically.
+5. Use scripts or structured data for repetitive work.
+6. Verify the result with build, tests, lint, browser checks, or direct inspection as appropriate.
+7. Update `.gaslighting/DECISION_LOG.md` when a product or technical decision changes.
+8. Update `.gaslighting/MISSING_INFO.md` when missing information is discovered or resolved.
+9. Update `.gaslighting/MEMORY.md` when stable project facts are learned.
+10. Update `.gaslighting/PROJECT_CARE.md` when GitHub, domain, deployment, env, analytics, email, or launch ownership changes.
+
+## Agent Rules
+
+- Do not ask the user for non-blocking information before starting work.
+- Do make a reasonable temporary assumption, document it, and continue.
+- Do not create only the visible surface and ignore operational details.
+- Do not stop at a plan when implementation was requested.
+- Do not call a scaffold complete.
+- Do not call TODO comments implementation.
+- Do not call examples full coverage.
+- Do not hide risk behind confident wording.
+- Do not over-engineer to look sophisticated.
+- Do not under-deliver because the work is repetitive.
+
+## Codex Execution Contract
+
+Before claiming completion, Codex must be able to answer:
+
+- What exact requested scope was completed?
+- What exact files changed?
+- What verification was run?
+- What assumptions are still active?
+- What missing information remains?
+- What care risks remain?
+- Is anything incomplete?
+
+If anything is incomplete, use the failure declaration protocol in `.gaslighting/GASLIGHTING.md`.

package/examples/ecommerce/.gaslighting/CODEX_PROMPT.md

@@ -14,7 +14,8 @@ Read the following files before doing any work:
 6. `.gaslighting/DECISION_LOG.md`
 7. `AGENTS.md`
 8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/PROJECT_CARE.md`
+9. `.gaslighting/AGENT_RUNTIME.md`
+10. `.gaslighting/PROJECT_CARE.md`
 
 Then implement the project MVP.
 

package/examples/ecommerce/AGENTS.md

@@ -13,8 +13,9 @@ Before doing any work, read these files in order:
 5. `.gaslighting/ASSUMPTIONS.md`
 6. `.gaslighting/DECISION_LOG.md`
 7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/PROJECT_CARE.md`
-9. `.gaslighting/AGENTS.md`
+8. `.gaslighting/AGENT_RUNTIME.md`
+9. `.gaslighting/PROJECT_CARE.md`
+10. `.gaslighting/AGENTS.md`
 
 Do not reduce scope.
 

package/examples/hospital-homepage/.codex/prompts/gaslighting.md

@@ -10,7 +10,8 @@ Read the Gaslighting-engine project-control files before doing any work:
 6. `.gaslighting/DECISION_LOG.md`
 7. `AGENTS.md`
 8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/PROJECT_CARE.md`
+9. `.gaslighting/AGENT_RUNTIME.md`
+10. `.gaslighting/PROJECT_CARE.md`
 
 Then execute the user's requested implementation.
 

package/examples/hospital-homepage/.codex/skills/gaslighting/SKILL.md

@@ -23,7 +23,8 @@ Instead:
 10. Generate `.gaslighting/DECISION_LOG.md`.
 11. Generate `.gaslighting/STACK_POLICY.md`.
 12. Generate or update root `AGENTS.md`.
-13. Generate `.gaslighting/PROJECT_CARE.md`.
+13. Generate `.gaslighting/AGENT_RUNTIME.md`.
+14. Generate `.gaslighting/PROJECT_CARE.md`.
 
 ## Hardcore Discipline Rule
 
@@ -92,6 +93,8 @@ Keep main project-control files in `.gaslighting/` and keep only the Codex point
 
 Use `.gaslighting/PROJECT_CARE.md` to track Git/GitHub/domain/deployment/launch risks without blocking implementation.
 
+Use `.gaslighting/AGENT_RUNTIME.md` to define the execution loop Codex must follow after the docs are generated.
+
 Do not only explain.
 
 Do not produce a plan without files.

package/examples/hospital-homepage/.gaslighting/AGENTS.md

@@ -11,7 +11,8 @@ Before doing any work, read these files in order:
 5. `.gaslighting/ASSUMPTIONS.md`
 6. `.gaslighting/DECISION_LOG.md`
 7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/PROJECT_CARE.md`
+8. `.gaslighting/AGENT_RUNTIME.md`
+9. `.gaslighting/PROJECT_CARE.md`
 
 ## Prime Directive
 
@@ -41,6 +42,7 @@ A task is complete only when:
 - New assumptions are documented.
 - New technical decisions are recorded.
 - Stable project facts are recorded in `.gaslighting/MEMORY.md`.
+- Runtime execution rules are preserved in `.gaslighting/AGENT_RUNTIME.md`.
 - Operational risks are recorded in `.gaslighting/PROJECT_CARE.md`.
 - The result does not contradict `.gaslighting/GASLIGHTING.md`.
 

package/examples/hospital-homepage/.gaslighting/AGENT_RUNTIME.md

@@ -0,0 +1,54 @@
+# AGENT_RUNTIME.md
+
+This file defines how Codex must operate after Gaslighting-engine prepares the project.
+
+It is not a suggestion file.
+
+It is the runtime loop.
+
+## Mission
+
+- Original request: I want to build a hospital website.
+- Project type: hospital_homepage
+- Classification confidence: medium
+- Runtime stance: Codex-first, full-scope, no fake completion.
+
+## Required Loop
+
+1. Read the control files before implementation.
+2. Restate the project purpose in one short paragraph.
+3. Convert the PRD into a concrete task checklist.
+4. Implement the checklist systematically.
+5. Use scripts or structured data for repetitive work.
+6. Verify the result with build, tests, lint, browser checks, or direct inspection as appropriate.
+7. Update `.gaslighting/DECISION_LOG.md` when a product or technical decision changes.
+8. Update `.gaslighting/MISSING_INFO.md` when missing information is discovered or resolved.
+9. Update `.gaslighting/MEMORY.md` when stable project facts are learned.
+10. Update `.gaslighting/PROJECT_CARE.md` when GitHub, domain, deployment, env, analytics, email, or launch ownership changes.
+
+## Agent Rules
+
+- Do not ask the user for non-blocking information before starting work.
+- Do make a reasonable temporary assumption, document it, and continue.
+- Do not create only the visible surface and ignore operational details.
+- Do not stop at a plan when implementation was requested.
+- Do not call a scaffold complete.
+- Do not call TODO comments implementation.
+- Do not call examples full coverage.
+- Do not hide risk behind confident wording.
+- Do not over-engineer to look sophisticated.
+- Do not under-deliver because the work is repetitive.
+
+## Codex Execution Contract
+
+Before claiming completion, Codex must be able to answer:
+
+- What exact requested scope was completed?
+- What exact files changed?
+- What verification was run?
+- What assumptions are still active?
+- What missing information remains?
+- What care risks remain?
+- Is anything incomplete?
+
+If anything is incomplete, use the failure declaration protocol in `.gaslighting/GASLIGHTING.md`.

package/examples/hospital-homepage/.gaslighting/CODEX_PROMPT.md

@@ -14,7 +14,8 @@ Read the following files before doing any work:
 6. `.gaslighting/DECISION_LOG.md`
 7. `AGENTS.md`
 8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/PROJECT_CARE.md`
+9. `.gaslighting/AGENT_RUNTIME.md`
+10. `.gaslighting/PROJECT_CARE.md`
 
 Then implement the project MVP.
 

package/examples/hospital-homepage/AGENTS.md

@@ -13,8 +13,9 @@ Before doing any work, read these files in order:
 5. `.gaslighting/ASSUMPTIONS.md`
 6. `.gaslighting/DECISION_LOG.md`
 7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/PROJECT_CARE.md`
-9. `.gaslighting/AGENTS.md`
+8. `.gaslighting/AGENT_RUNTIME.md`
+9. `.gaslighting/PROJECT_CARE.md`
+10. `.gaslighting/AGENTS.md`
 
 Do not reduce scope.
 

package/examples/landing-page/.codex/prompts/gaslighting.md

@@ -10,7 +10,8 @@ Read the Gaslighting-engine project-control files before doing any work:
 6. `.gaslighting/DECISION_LOG.md`
 7. `AGENTS.md`
 8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/PROJECT_CARE.md`
+9. `.gaslighting/AGENT_RUNTIME.md`
+10. `.gaslighting/PROJECT_CARE.md`
 
 Then execute the user's requested implementation.
 

package/examples/landing-page/.codex/skills/gaslighting/SKILL.md

@@ -23,7 +23,8 @@ Instead:
 10. Generate `.gaslighting/DECISION_LOG.md`.
 11. Generate `.gaslighting/STACK_POLICY.md`.
 12. Generate or update root `AGENTS.md`.
-13. Generate `.gaslighting/PROJECT_CARE.md`.
+13. Generate `.gaslighting/AGENT_RUNTIME.md`.
+14. Generate `.gaslighting/PROJECT_CARE.md`.
 
 ## Hardcore Discipline Rule
 
@@ -92,6 +93,8 @@ Keep main project-control files in `.gaslighting/` and keep only the Codex point
 
 Use `.gaslighting/PROJECT_CARE.md` to track Git/GitHub/domain/deployment/launch risks without blocking implementation.
 
+Use `.gaslighting/AGENT_RUNTIME.md` to define the execution loop Codex must follow after the docs are generated.
+
 Do not only explain.
 
 Do not produce a plan without files.

package/examples/landing-page/.gaslighting/AGENTS.md

@@ -11,7 +11,8 @@ Before doing any work, read these files in order:
 5. `.gaslighting/ASSUMPTIONS.md`
 6. `.gaslighting/DECISION_LOG.md`
 7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/PROJECT_CARE.md`
+8. `.gaslighting/AGENT_RUNTIME.md`
+9. `.gaslighting/PROJECT_CARE.md`
 
 ## Prime Directive
 
@@ -41,6 +42,7 @@ A task is complete only when:
 - New assumptions are documented.
 - New technical decisions are recorded.
 - Stable project facts are recorded in `.gaslighting/MEMORY.md`.
+- Runtime execution rules are preserved in `.gaslighting/AGENT_RUNTIME.md`.
 - Operational risks are recorded in `.gaslighting/PROJECT_CARE.md`.
 - The result does not contradict `.gaslighting/GASLIGHTING.md`.
 

package/examples/landing-page/.gaslighting/AGENT_RUNTIME.md

@@ -0,0 +1,54 @@
+# AGENT_RUNTIME.md
+
+This file defines how Codex must operate after Gaslighting-engine prepares the project.
+
+It is not a suggestion file.
+
+It is the runtime loop.
+
+## Mission
+
+- Original request: Build a landing page for a new service that captures leads.
+- Project type: landing_page
+- Classification confidence: high
+- Runtime stance: Codex-first, full-scope, no fake completion.
+
+## Required Loop
+
+1. Read the control files before implementation.
+2. Restate the project purpose in one short paragraph.
+3. Convert the PRD into a concrete task checklist.
+4. Implement the checklist systematically.
+5. Use scripts or structured data for repetitive work.
+6. Verify the result with build, tests, lint, browser checks, or direct inspection as appropriate.
+7. Update `.gaslighting/DECISION_LOG.md` when a product or technical decision changes.
+8. Update `.gaslighting/MISSING_INFO.md` when missing information is discovered or resolved.
+9. Update `.gaslighting/MEMORY.md` when stable project facts are learned.
+10. Update `.gaslighting/PROJECT_CARE.md` when GitHub, domain, deployment, env, analytics, email, or launch ownership changes.
+
+## Agent Rules
+
+- Do not ask the user for non-blocking information before starting work.
+- Do make a reasonable temporary assumption, document it, and continue.
+- Do not create only the visible surface and ignore operational details.
+- Do not stop at a plan when implementation was requested.
+- Do not call a scaffold complete.
+- Do not call TODO comments implementation.
+- Do not call examples full coverage.
+- Do not hide risk behind confident wording.
+- Do not over-engineer to look sophisticated.
+- Do not under-deliver because the work is repetitive.
+
+## Codex Execution Contract
+
+Before claiming completion, Codex must be able to answer:
+
+- What exact requested scope was completed?
+- What exact files changed?
+- What verification was run?
+- What assumptions are still active?
+- What missing information remains?
+- What care risks remain?
+- Is anything incomplete?
+
+If anything is incomplete, use the failure declaration protocol in `.gaslighting/GASLIGHTING.md`.

package/examples/landing-page/.gaslighting/CODEX_PROMPT.md

@@ -14,7 +14,8 @@ Read the following files before doing any work:
 6. `.gaslighting/DECISION_LOG.md`
 7. `AGENTS.md`
 8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/PROJECT_CARE.md`
+9. `.gaslighting/AGENT_RUNTIME.md`
+10. `.gaslighting/PROJECT_CARE.md`
 
 Then implement the project MVP.
 

package/examples/landing-page/AGENTS.md

@@ -13,8 +13,9 @@ Before doing any work, read these files in order:
 5. `.gaslighting/ASSUMPTIONS.md`
 6. `.gaslighting/DECISION_LOG.md`
 7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/PROJECT_CARE.md`
-9. `.gaslighting/AGENTS.md`
+8. `.gaslighting/AGENT_RUNTIME.md`
+9. `.gaslighting/PROJECT_CARE.md`
+10. `.gaslighting/AGENTS.md`
 
 Do not reduce scope.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gaslighting-engine",
-  "version": "0.2.2",
+  "version": "0.3.0",
   "description": "LUDGI Gaslighting-engine: a hardcore project-discipline generator for AI coding agents.",
   "type": "module",
   "license": "MIT",