gaslighting-engine 0.3.1 → 0.4.1

package/examples/hospital-homepage/.gaslighting/product/PAGE_MAP.md

@@ -0,0 +1,9 @@
+# Page Map
+
+- [ ] Home: define purpose, content, CTA, empty state, and acceptance criteria.
+- [ ] Hospital Introduction: define purpose, content, CTA, empty state, and acceptance criteria.
+- [ ] Departments / Treatments: define purpose, content, CTA, empty state, and acceptance criteria.
+- [ ] Doctor Profiles: define purpose, content, CTA, empty state, and acceptance criteria.
+- [ ] Consultation / Contact: define purpose, content, CTA, empty state, and acceptance criteria.
+- [ ] Location: define purpose, content, CTA, empty state, and acceptance criteria.
+- [ ] Privacy Policy: define purpose, content, CTA, empty state, and acceptance criteria.

package/examples/hospital-homepage/.gaslighting/product/PRD.md

@@ -0,0 +1,119 @@
+# PRD.md
+
+## 1. Product Overview
+
+Build an MVP for this request:
+
+> I want to build a hospital website.
+
+Classified project type: `hospital_homepage`
+
+The product must preserve the user's actual scope and must not become a decorative shell.
+
+## 2. Business Purpose
+
+- increase trust
+- generate consultation inquiries
+- support reservation conversion
+- make departments and treatments understandable
+- make doctors and hospital credibility visible
+- help mobile visitors contact the hospital quickly
+- support local SEO
+- make location and contact information obvious
+
+## 3. Target Users
+
+- Potential patients searching on mobile
+- Patients comparing hospitals
+- Users looking for treatment information
+- Users who want to call, reserve, or ask questions
+- Hospital staff receiving inquiries
+
+## 4. User Flows
+
+- Search/mobile visitor -> home -> treatment/doctor trust -> contact or reservation CTA
+- Visitor -> location/contact -> call or submit inquiry
+
+## 5. Page List
+
+- Home
+- Hospital Introduction
+- Departments / Treatments
+- Doctor Profiles
+- Consultation / Contact
+- Location
+- Privacy Policy
+
+## 6. Feature List
+
+- responsive layout
+- mobile-first UI
+- contact CTA
+- inquiry form
+- treatment sections
+- doctor introduction
+- location section
+- privacy policy
+- SEO metadata
+- analytics-ready structure
+
+## 7. Data Model Draft
+
+- Inquiry: name, phone, category, message, privacyConsent, status, createdAt
+- Treatment: title, summary, body, image, order
+- Doctor: name, specialty, bio, credentials, image
+- Location: address, phone, hours, mapUrl
+
+## 8. MVP Scope
+
+- Implement all pages, flows, and features listed above.
+- Include responsive behavior.
+- Include useful empty, loading, success, and error states where applicable.
+- Include SEO metadata where public pages exist.
+- Include analytics-ready structure where conversion matters.
+- Document every assumption that affects implementation.
+
+## 9. Out of Scope
+
+- full admin dashboard
+- payment
+- complex reservation calendar
+- EMR integration
+- user login
+- multilingual content
+- automated medical diagnosis
+
+## 10. Non-Functional Requirements
+
+- Mobile-first where users are likely to arrive from search or ads.
+- Accessible semantic HTML.
+- Fast initial load for public pages.
+- Safe form validation and clear error messages.
+- Maintainable TypeScript structure.
+- No unnecessary distributed systems.
+
+## 11. Tech Stack
+
+No stack hints were provided. Use the default practical web stack unless the user later changes it.
+
+See `STACK_POLICY.md` for defaults and forbidden-by-default technology.
+
+## 12. Risks
+
+- Vague source requirements can cause wrong vertical assumptions.
+- Placeholder copy can look real if not reviewed.
+- Missing production credentials can block deployment.
+- AI agents may reduce scope unless `GASLIGHTING.md` is enforced.
+
+## 13. Missing Information
+
+See `MISSING_INFO.md`.
+
+## 14. Success Criteria
+
+- The project purpose is visible in the implemented product.
+- The core pages and features are implemented, not merely described.
+- No required scope is replaced by representative examples.
+- No TODO is used as a substitute for implementation.
+- Assumptions and decisions remain documented.
+- The output can actually be used for the MVP purpose.

package/examples/hospital-homepage/.gaslighting/product/USER_FLOWS.md

@@ -0,0 +1,20 @@
+# User Flows
+
+Project type: `hospital_homepage`
+
+## Primary Flow
+
+1. User lands on the first relevant page.
+2. User understands the offer or purpose quickly.
+3. User explores the page or feature set needed for trust and decision-making.
+4. User completes the primary conversion or operational action.
+
+## Page Coverage
+
+1. Home
+2. Hospital Introduction
+3. Departments / Treatments
+4. Doctor Profiles
+5. Consultation / Contact
+6. Location
+7. Privacy Policy

package/examples/hospital-homepage/.gaslighting/tasks/TASK-0001.md

@@ -0,0 +1,17 @@
+# TASK-0001: Initialize Mission Scope
+
+Status: pending
+Runtime: codex
+Permission mode: auto_review
+
+## Goal
+
+Turn the original request into implemented project work without fake completion.
+
+## Request
+
+> I want to build a hospital website.
+
+## Project Type
+
+`hospital_homepage`

package/examples/hospital-homepage/.gaslighting/verification/latest-report.md

@@ -0,0 +1,3 @@
+# Latest Verification Report
+
+No verification has run yet.

package/examples/hospital-homepage/AGENTS.md

@@ -4,18 +4,20 @@ This repository uses Gaslighting-engine.
 
 The main discipline documents live under `.gaslighting/` to avoid cluttering the project root.
 
+Start with `.gaslighting/INDEX.md`. It points to the mission, product, feature, operation, task, loop, verification, and memory documents.
+
 Before doing any work, read these files in order:
 
-1. `.gaslighting/GASLIGHTING.md`
-2. `.gaslighting/PRD.md`
-3. `.gaslighting/STACK_POLICY.md`
-4. `.gaslighting/MISSING_INFO.md`
-5. `.gaslighting/ASSUMPTIONS.md`
-6. `.gaslighting/DECISION_LOG.md`
-7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/AGENT_RUNTIME.md`
-9. `.gaslighting/PROJECT_CARE.md`
-10. `.gaslighting/AGENTS.md`
+1. `.gaslighting/INDEX.md`
+2. `.gaslighting/mission/PROJECT_PURPOSE.md`
+3. `.gaslighting/mission/EXECUTION_RULES.md`
+4. `.gaslighting/mission/COMPLETION_STANDARD.md`
+5. `.gaslighting/product/PRD.md`
+6. `.gaslighting/product/PAGE_MAP.md`
+7. `.gaslighting/features/core-scope/TASKS.md`
+8. `.gaslighting/operations/PROJECT_CARE.md`
+9. `.gaslighting/loops/current-session.json`
+10. `.gaslighting/GASLIGHTING.md`
 
 Do not reduce scope.
 

package/examples/landing-page/.agents/config.json

@@ -0,0 +1,10 @@
+{
+  "sourceOfTruth": true,
+  "defaultRuntime": "codex",
+  "permissionMode": "auto_review",
+  "exports": [
+    ".codex"
+  ],
+  "skillRoot": ".agents/skills",
+  "mcpRoot": ".agents/mcp"
+}

package/examples/landing-page/.agents/mcp/manifest.json

@@ -0,0 +1,5 @@
+{
+  "servers": [],
+  "installedAt": null,
+  "source": ".agents/mcp"
+}

package/examples/landing-page/.agents/runtimes/claude.json

@@ -0,0 +1,6 @@
+{
+  "id": "claude",
+  "enabled": false,
+  "supportsMcp": true,
+  "supportsSkills": true
+}

package/examples/landing-page/.agents/runtimes/codex.json

@@ -0,0 +1,6 @@
+{
+  "id": "codex",
+  "enabled": true,
+  "supportsMcp": true,
+  "supportsSkills": true
+}

package/examples/landing-page/.agents/runtimes/kimi.json

@@ -0,0 +1,6 @@
+{
+  "id": "kimi",
+  "enabled": false,
+  "supportsMcp": true,
+  "supportsSkills": true
+}

package/examples/landing-page/.agents/runtimes/local.json

@@ -0,0 +1,6 @@
+{
+  "id": "local",
+  "enabled": false,
+  "supportsMcp": false,
+  "supportsSkills": false
+}

package/examples/landing-page/.agents/runtimes/openai_compatible.json

@@ -0,0 +1,6 @@
+{
+  "id": "openai_compatible",
+  "enabled": false,
+  "supportsMcp": false,
+  "supportsSkills": false
+}

package/examples/landing-page/.agents/runtimes/opencode.json

@@ -0,0 +1,6 @@
+{
+  "id": "opencode",
+  "enabled": false,
+  "supportsMcp": true,
+  "supportsSkills": false
+}

package/examples/landing-page/.agents/runtimes/qwen.json

@@ -0,0 +1,6 @@
+{
+  "id": "qwen",
+  "enabled": false,
+  "supportsMcp": true,
+  "supportsSkills": false
+}

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

@@ -2,16 +2,16 @@
 
 Read the Gaslighting-engine project-control files before doing any work:
 
-1. `.gaslighting/GASLIGHTING.md`
-2. `.gaslighting/PRD.md`
-3. `.gaslighting/STACK_POLICY.md`
-4. `.gaslighting/MISSING_INFO.md`
-5. `.gaslighting/ASSUMPTIONS.md`
-6. `.gaslighting/DECISION_LOG.md`
+1. `.gaslighting/INDEX.md`
+2. `.gaslighting/mission/PROJECT_PURPOSE.md`
+3. `.gaslighting/mission/EXECUTION_RULES.md`
+4. `.gaslighting/product/PRD.md`
+5. `.gaslighting/features/core-scope/TASKS.md`
+6. `.gaslighting/operations/PROJECT_CARE.md`
 7. `AGENTS.md`
-8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/AGENT_RUNTIME.md`
-10. `.gaslighting/PROJECT_CARE.md`
+8. `.gaslighting/GASLIGHTING.md`
+9. `.gaslighting/MISSING_INFO.md`
+10. `.gaslighting/DECISION_LOG.md`
 
 Then execute the user's requested implementation.
 

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

@@ -4,15 +4,15 @@ This repository uses Gaslighting-engine.
 
 Before doing any work, read these files in order:
 
-1. `.gaslighting/GASLIGHTING.md`
-2. `.gaslighting/PRD.md`
-3. `.gaslighting/STACK_POLICY.md`
-4. `.gaslighting/MISSING_INFO.md`
-5. `.gaslighting/ASSUMPTIONS.md`
-6. `.gaslighting/DECISION_LOG.md`
-7. `.gaslighting/MEMORY.md`
-8. `.gaslighting/AGENT_RUNTIME.md`
-9. `.gaslighting/PROJECT_CARE.md`
+1. `.gaslighting/INDEX.md`
+2. `.gaslighting/mission/PROJECT_PURPOSE.md`
+3. `.gaslighting/mission/EXECUTION_RULES.md`
+4. `.gaslighting/mission/COMPLETION_STANDARD.md`
+5. `.gaslighting/product/PRD.md`
+6. `.gaslighting/features/core-scope/TASKS.md`
+7. `.gaslighting/operations/PROJECT_CARE.md`
+8. `.gaslighting/loops/current-session.json`
+9. `.gaslighting/GASLIGHTING.md`
 
 ## Prime Directive
 

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

@@ -8,7 +8,7 @@ It is the runtime loop.
 
 ## Mission
 
-- Original request: Build a landing page for a new service that captures leads.
+- Original request: Build a landing page for lead capture.
 - Project type: landing_page
 - Classification confidence: high
 - Runtime stance: Codex-first, full-scope, no fake completion.

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

@@ -6,16 +6,16 @@ Copy and paste this into Codex:
 
 Read the following files before doing any work:
 
-1. `.gaslighting/GASLIGHTING.md`
-2. `.gaslighting/PRD.md`
-3. `.gaslighting/STACK_POLICY.md`
-4. `.gaslighting/MISSING_INFO.md`
-5. `.gaslighting/ASSUMPTIONS.md`
-6. `.gaslighting/DECISION_LOG.md`
+1. `.gaslighting/INDEX.md`
+2. `.gaslighting/mission/PROJECT_PURPOSE.md`
+3. `.gaslighting/mission/EXECUTION_RULES.md`
+4. `.gaslighting/product/PRD.md`
+5. `.gaslighting/features/core-scope/TASKS.md`
+6. `.gaslighting/operations/PROJECT_CARE.md`
 7. `AGENTS.md`
-8. `.gaslighting/MEMORY.md`
-9. `.gaslighting/AGENT_RUNTIME.md`
-10. `.gaslighting/PROJECT_CARE.md`
+8. `.gaslighting/GASLIGHTING.md`
+9. `.gaslighting/MISSING_INFO.md`
+10. `.gaslighting/DECISION_LOG.md`
 
 Then implement the project MVP.
 

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

@@ -8,7 +8,7 @@ Date: 2026-05-23
 
 Generate strict Gaslighting-engine project-control documents for the request:
 
-> Build a landing page for a new service that captures leads.
+> Build a landing page for lead capture.
 
 ### Reason
 

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

@@ -121,7 +121,7 @@ Project type: `landing_page`
 
 Original request:
 
-> Build a landing page for a new service that captures leads.
+> Build a landing page for lead capture.
 
 The purpose is:
 
@@ -139,7 +139,7 @@ The purpose is:
 
 ## 3. Confirmed Information
 
-- The user requested: Build a landing page for a new service that captures leads.
+- The user requested: Build a landing page for lead capture.
 - Classified project type: landing_page
 - Classification confidence: high
 - No stack hints were provided. Use the default practical web stack unless the user later changes it.

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

@@ -0,0 +1,31 @@
+# Gaslighting-engine Index
+
+This is the structured source of truth for the project discipline layer.
+
+## Mission
+
+- Original request: Build a landing page for lead capture.
+- Project type: landing_page
+- Classification confidence: high
+- Default runtime: codex
+- Loop mode: off
+- Permission mode: auto_review
+
+## Read Order For Agents
+
+1. `mission/PROJECT_PURPOSE.md`
+2. `mission/EXECUTION_RULES.md`
+3. `mission/COMPLETION_STANDARD.md`
+4. `product/PRD.md`
+5. `product/PAGE_MAP.md`
+6. `features/core-scope/TASKS.md`
+7. `operations/PROJECT_CARE.md`
+8. `loops/current-session.json`
+
+## Pages
+
+- Single landing page with Hero, Problem, Solution, Benefits, Social Proof, Process, Offer, FAQ, Final CTA, Lead Form
+
+## Compatibility Files
+
+Older agents may still read the root compatibility markdown files in `.gaslighting/`. Those files remain generated for backward compatibility, but this index is the preferred entrypoint.

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

@@ -10,7 +10,7 @@ Keep required rules in root `AGENTS.md`, `.gaslighting/GASLIGHTING.md`, and chec
 
 ## Stable Project Facts
 
-- Original request: Build a landing page for a new service that captures leads.
+- Original request: Build a landing page for lead capture.
 - Project type: landing_page
 - Classification confidence: high
 - Stack hints: none

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

@@ -4,7 +4,7 @@
 
 Build an MVP for this request:
 
-> Build a landing page for a new service that captures leads.
+> Build a landing page for lead capture.
 
 Classified project type: `landing_page`
 

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

@@ -11,7 +11,7 @@ The agent must treat this project as mission-critical. If something can put deli
 ## Project Snapshot
 
 - Date: 2026-05-23
-- Original request: Build a landing page for a new service that captures leads.
+- Original request: Build a landing page for lead capture.
 - Project type: landing_page
 - Classification confidence: high
 - Project purpose:

package/examples/landing-page/.gaslighting/checkpoints/latest.md

@@ -0,0 +1,7 @@
+# Latest Checkpoint
+
+No loop iteration has completed yet.
+
+Original request:
+
+> Build a landing page for lead capture.

package/examples/landing-page/.gaslighting/config.json

@@ -0,0 +1,7 @@
+{
+  "defaultRuntime": "codex",
+  "loopMode": "off",
+  "permissionMode": "auto_review",
+  "skillSource": ".agents",
+  "documentLayout": "structured"
+}

package/examples/landing-page/.gaslighting/decisions/ADR-0001-stack.md

@@ -0,0 +1,11 @@
+# ADR-0001: Stack Policy
+
+Date: 2026-05-23
+
+## Decision
+
+No stack hints were provided. Use the default practical web stack unless the user later changes it.
+
+## Consequence
+
+The agent must avoid over-engineering and choose technology that serves the project purpose.

package/examples/landing-page/.gaslighting/decisions/ADR-0002-agent-runtime.md

@@ -0,0 +1,11 @@
+# ADR-0002: Agent Runtime
+
+Date: 2026-05-23
+
+## Decision
+
+Default runtime is `codex`.
+
+Loop mode defaults to `off`.
+
+Permission mode defaults to `auto_review`.

package/examples/landing-page/.gaslighting/features/core-scope/DECISIONS.md

@@ -0,0 +1,5 @@
+# Feature Decisions
+
+- Project type initialized as `landing_page`.
+- Deterministic template generation is used instead of an LLM API.
+- Scope preservation is mandatory.

package/examples/landing-page/.gaslighting/features/core-scope/FEATURE.md

@@ -0,0 +1,7 @@
+# Core Scope Feature
+
+Original request: Build a landing page for lead capture.
+
+This feature captures the complete MVP scope for `landing_page`.
+
+The agent must not reduce it to a sample, scaffold, or visual-only shell.

package/examples/landing-page/.gaslighting/features/core-scope/RISKS.md

@@ -0,0 +1,5 @@
+# Feature Risks
+
+- Classification confidence: high
+- Missing information can affect copy, data model, page details, and production readiness.
+- Repetitive surfaces are at risk of being summarized instead of implemented.

package/examples/landing-page/.gaslighting/features/core-scope/TASKS.md

@@ -0,0 +1,11 @@
+# Core Scope Tasks
+
+- [ ] Preserve and restate the project purpose for `landing_page`.
+- [ ] Implement all required MVP pages or feature surfaces.
+- [ ] Implement and verify page/surface: Single landing page with Hero, Problem, Solution, Benefits, Social Proof, Process, Offer, FAQ, Final CTA, Lead Form
+- [ ] Verify build/test/lint/browser flow as appropriate.
+- [ ] Update decisions, missing info, memory, and project care files.
+
+Original request:
+
+> Build a landing page for lead capture.

package/examples/landing-page/.gaslighting/loops/current-session.json

@@ -0,0 +1,9 @@
+{
+  "active": false,
+  "status": "off",
+  "currentTask": "TASK-0001",
+  "runtime": "codex",
+  "permissionMode": "auto_review",
+  "iterations": 0,
+  "stopRequested": false
+}

package/examples/landing-page/.gaslighting/memory/OPEN_QUESTIONS.md

@@ -0,0 +1,5 @@
+# Open Questions
+
+- Exact offer and conversion goal: Confirm the offer, target audience, ad source, CTA, and lead destination.
+- Final brand identity and production copy: Collect final brand name, tone, assets, and legally approved copy before launch.
+- Exact deployment credentials and accounts: Add project-specific env vars and provider accounts before production deployment.

package/examples/landing-page/.gaslighting/memory/PROJECT_MEMORY.md

@@ -0,0 +1,5 @@
+# Project Memory
+
+- Original request: Build a landing page for lead capture.
+- Project type: landing_page
+- Classification confidence: high

package/examples/landing-page/.gaslighting/memory/SESSION_LOG.md

@@ -0,0 +1,3 @@
+# Session Log
+
+- 2026-05-23: Gaslighting-engine structured mission initialized for: Build a landing page for lead capture.

package/examples/landing-page/.gaslighting/mission/COMPLETION_STANDARD.md

@@ -0,0 +1,11 @@
+# Completion Standard
+
+A task is complete only when:
+
+- Requested scope is fully handled.
+- No required item was silently skipped.
+- No placeholder is pretending to be implementation.
+- No TODO replaces requested implementation.
+- Verification was run or the reason it could not run is stated.
+- Assumptions, missing information, and operational care risks are updated.
+- The result can actually be used.

package/examples/landing-page/.gaslighting/mission/EXECUTION_RULES.md

@@ -0,0 +1,20 @@
+# Execution Rules
+
+- Runtime: codex
+- Loop mode: off
+- Permission mode: auto_review
+
+## Non-Negotiables
+
+- Do the actual work.
+- Do not shrink scope.
+- Do not use TODOs as fake implementation.
+- Do not present representative examples as full coverage.
+- Document missing information and continue unless truly blocked.
+- Record operational risk in `operations/PROJECT_CARE.md`.
+
+## Permission Modes
+
+- `ask_each_task`: request approval before each task action.
+- `auto_review`: continue ordinary work; request approval for destructive, publishing, deployment, secret, DNS, payment, MCP install, or global configuration changes.
+- `full_autonomy`: continue without approval, but log every action and never expose secrets.

package/examples/landing-page/.gaslighting/mission/PROJECT_PURPOSE.md

@@ -0,0 +1,19 @@
+# Project Purpose
+
+Original request:
+
+> Build a landing page for lead capture.
+
+Project type: `landing_page`
+
+The purpose is:
+
+- make the offer clear within 5 seconds
+- drive CTA clicks
+- capture leads
+- support ad traffic
+- reduce bounce
+- communicate value clearly
+- load fast on mobile
+
+Do not turn this project into a generic showcase. Preserve the business purpose and conversion/operation goals implied by the project type.

package/examples/landing-page/.gaslighting/operations/DEPLOYMENT.md

@@ -0,0 +1,6 @@
+# Deployment Operations
+
+- Deployment provider: unconfirmed until detected or selected.
+- Preview URL policy: missing until confirmed.
+- Rollback path: missing until confirmed.
+- Deployment commands require approval in auto-review mode.

package/examples/landing-page/.gaslighting/operations/DOMAIN.md

@@ -0,0 +1,6 @@
+# Domain Operations
+
+- Production domain: missing until confirmed.
+- DNS provider: missing until confirmed.
+- Domain owner: missing until confirmed.
+- Do not treat missing domain data as implementation-blocking unless launch is requested.

package/examples/landing-page/.gaslighting/operations/ENV.md

@@ -0,0 +1,5 @@
+# Environment Operations
+
+- Keep real secrets out of generated documents.
+- Prefer `.env.example` for required variables.
+- Secret changes require approval in auto-review mode.