gaslighting-engine 0.1.0

package/examples/hospital-homepage/ASSUMPTIONS.md

@@ -0,0 +1,218 @@
+# ASSUMPTIONS.md
+
+## Assumption: Hospital name Sample Clinic
+
+Status: Active
+Confidence: Medium
+Impact: High
+
+### Why this assumption was made
+
+Hospital name: Sample Clinic.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+
+## Assumption: Hospital type dermatology/aesthetic clinic
+
+Status: Active
+Confidence: Medium
+Impact: Medium
+
+### Why this assumption was made
+
+Hospital type: dermatology/aesthetic clinic.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+
+## Assumption: Location Seoul area
+
+Status: Active
+Confidence: Medium
+Impact: Medium
+
+### Why this assumption was made
+
+Location: Seoul area.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+
+## Assumption: Main goal trust, consultation inquiries, reservations, local SEO, and mobile con
+
+Status: Active
+Confidence: Medium
+Impact: Medium
+
+### Why this assumption was made
+
+Main goal: trust, consultation inquiries, reservations, local SEO, and mobile contact clarity.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+
+## Assumption: Admin dashboard is excluded from MVP unless requested later
+
+Status: Active
+Confidence: Medium
+Impact: Medium
+
+### Why this assumption was made
+
+Admin dashboard is excluded from MVP unless requested later.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+
+## Assumption: Medical ad copy requires human review before production
+
+Status: Active
+Confidence: Medium
+Impact: Medium
+
+### Why this assumption was made
+
+Medical ad copy requires human review before production.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+
+## Assumption: Use the default practical web stack unless the user later specifies otherwise
+
+Status: Active
+Confidence: Medium
+Impact: Medium
+
+### Why this assumption was made
+
+Use the default practical web stack unless the user later specifies otherwise.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+
+## Assumption: Build an MVP that can be implemented locally without a SaaS backend for this gen
+
+Status: Active
+Confidence: Medium
+Impact: Medium
+
+### Why this assumption was made
+
+Build an MVP that can be implemented locally without a SaaS backend for this generator.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+
+## Assumption: Treat unspecified brand/content details as temporary copy that must be human-rev
+
+Status: Active
+Confidence: Medium
+Impact: Medium
+
+### Why this assumption was made
+
+Treat unspecified brand/content details as temporary copy that must be human-reviewed before production.
+
+The user did not provide enough confirmed detail to treat this as fact.
+
+### What could make this wrong
+
+The user provides a different business model, vertical, stack, audience, market, or production constraint.
+
+### What changes if this assumption is wrong
+
+The PRD, page list, data model, implementation priorities, and copy may need to change.
+
+### How to replace this assumption
+
+Provide confirmed information and run `gaslighting update "new information here"`.
+

package/examples/hospital-homepage/CODEX_PROMPT.md

@@ -0,0 +1,34 @@
+# CODEX_PROMPT.md
+
+Copy and paste this into Codex:
+
+---
+
+Read the following files before doing any work:
+
+1. `GASLIGHTING.md`
+2. `PRD.md`
+3. `STACK_POLICY.md`
+4. `MISSING_INFO.md`
+5. `ASSUMPTIONS.md`
+6. `DECISION_LOG.md`
+7. `AGENTS.md`
+8. `MEMORY.md`
+
+Then implement the project MVP.
+
+Rules:
+
+- Do not shrink the scope.
+- Do not leave TODOs instead of implementation.
+- Do not implement only representative examples.
+- Do not say "the rest follows the same pattern."
+- Do not call scaffolding completion.
+- Do not call placeholders implementation.
+- Do not over-engineer.
+- Do not forget the project purpose.
+- If something is incomplete, declare it explicitly.
+
+Before claiming completion, perform the self-audit in `GASLIGHTING.md`.
+
+Proceed.

package/examples/hospital-homepage/DECISION_LOG.md

@@ -0,0 +1,95 @@
+# DECISION_LOG.md
+
+## Decision: Initialize Gaslighting documents
+
+Date: 2026-05-23
+
+### Decision
+
+Generate strict Gaslighting-engine project-control documents for the request:
+
+> I want to build a hospital website.
+
+### Reason
+
+The project needs AI-agent discipline before implementation so the agent does not drift, shrink scope, leave TODOs, or fake completion.
+
+### Alternatives Considered
+
+- Start coding without discipline documents.
+- Ask the user a long list of questions before making progress.
+- Use an LLM API to generate custom documents.
+
+### Why Alternatives Were Not Chosen
+
+- Coding without control documents increases fake-completion risk.
+- Most missing information can be assumed and documented.
+- MVP must be deterministic and must not call an LLM API.
+
+### Risk
+
+The initial project type or assumptions may be wrong.
+
+### Revisit When
+
+The user provides confirmed business details, stack choices, scope changes, or production constraints.
+
+## Decision: Project type classification
+
+Date: 2026-05-23
+
+### Decision
+
+Classified project type as `hospital_homepage` with `medium` confidence.
+
+### Reason
+
+Keyword-based classification is deterministic and enough for MVP.
+
+### Alternatives Considered
+
+- Ask the user to classify the project manually.
+- Use an external LLM API.
+
+### Why Alternatives Were Not Chosen
+
+- Manual classification slows progress.
+- External LLM APIs are excluded from MVP.
+
+### Risk
+
+Low-confidence classification can create the wrong project-specific template.
+
+### Revisit When
+
+The user says the project type is different or adds a clearer project description.
+
+## Decision: Stack policy
+
+Date: 2026-05-23
+
+### Decision
+
+No stack hints were provided. Use the default practical web stack unless the user later changes it.
+
+### Reason
+
+Technology must serve the product purpose and avoid over-engineering.
+
+### Alternatives Considered
+
+- Introduce advanced infrastructure up front.
+- Leave stack completely undefined.
+
+### Why Alternatives Were Not Chosen
+
+- Advanced infrastructure is forbidden by default.
+- Undefined stack choices allow drift and inconsistent agent behavior.
+
+### Risk
+
+Production needs may require a provider change later.
+
+### Revisit When
+
+Deployment provider, database provider, storage, analytics, email, or payment requirements are confirmed.