This repository is read-only and no longer maintained.
- Why? genesis was a prototype for document generation apps. It has been fully replaced by the production-ready, actively developed docforge-ai.
- Where to go now? Fork, star, contribute, or use code from https://github.com/bordenet/docforge-ai (most recent commits, features, and job-description tooling).
- Migration details: All core logic, improvements, and new features (e.g., job-description fortification) are in docforge-ai. Historical genesis code remains here for reference.
- Last updated: 2026-02-15.
[Original genesis README content below...]
Ecosystem of AI-powered document assistants and validators using a paired architecture.
Named for the Genesis Planet in Star Trek II: The Wrath of Khan, the life-creating world born from the Mutara Nebula where Spock's torpedo lands. No biblical reference intended; pure sci-fi homage to rapid, emergent creation.
Genesis started as an experiment: how deterministic could I make AI-assisted development? The answer: not very! I was fighting nature at every turn. Traditional architecture with AI-generated code on a short leash wins. A useful exercise that revealed how much mutation even the best AI coding agents introduce. See BACKGROUND.md for the full story.
Genesis was an experiment in deterministic AI-assisted development. The conclusion: architecture-first design with AI iteration beats conformity tooling.
| Metric | Finding | Source |
|---|---|---|
| Developer productivity | 26% boost from AI coding assistants | IT Revolution |
| PR cycle speed | 20-24% faster on routine tasks | dev.to |
| Complex logic | 10-19% slower due to debugging "almost-right" code | dev.to |
| Prototype velocity | 16-26% boost for MVPs (3-4 week cycles) | Coaio |
| AI adoption | 60%+ of companies using AI across multiple functions | |
| AI agent focus time | Doubling every 7 months (METR data) |
- Architecture first, AI second: Define structure upfront, let AI handle implementation details
- Speed vs. quality trade-offs are real: Rapid prototyping via AI, human oversight on reliability and security
- Context engineering matters: Dedicated files (AGENTS.md, structured prompts) guide AI behavior better than long instructions
- Tests as guardrails: Comprehensive coverage catches regressions without mandating line-by-line review
Genesis pushed conformity tooling to its limits: 1,600+ commits, 9 repositories, byte-for-byte diff tools, self-reinforcing AI instructions. It worked, but the maintenance burden compounded. Every improvement required propagation to 9 derived projects.
The better approach: A unified codebase with plugin architecture. Shared infrastructure, isolated data, one test suite. This is DocForgeAI.
Every genesis-tools project contains BOTH:
| Component | Purpose | Location |
|---|---|---|
| Assistant | 3-phase AI workflow for creating documents | assistant/ |
| Validator | Score documents against quality dimensions | validator/ |
Shared Libraries (copied into each project's js/core/ directory):
assistant-core- UI, storage, workflow utilitiesvalidator-core- UI, storage, scoring utilities
See ARCHITECTURE.md for full details on the paired model.
| Project | Document Type | Assistant | Validator |
|---|---|---|---|
| one-pager | One-Pager | ||
| pr-faq-assistant | PR-FAQ | ||
| product-requirements-assistant | PRD | ||
| power-statement-assistant | Power Statement | ||
| strategic-proposal | Strategic Proposal | ||
| architecture-decision-record | ADR | ||
| jd-assistant | Job Description | ||
| acceptance-criteria-assistant | Acceptance Criteria | ||
| business-justification-assistant | Business Justification |
9 paired projects, each with 90%+ test coverage and CI/CD.
Note: These tools currently exist as separate repositories with a shared codebase. Enterprise deployment options (monorepo, unified portal, etc.) are under consideration.
Follow the step-by-step guide in genesis/START-HERE.md.
This creates a new project with:
assistant/- 3-phase workflow appvalidator/- Document scorer- Pre-configured Jest, ESLint, GitHub Actions
For quick prototyping, copy the hello-world template:
# Copy the paired template
cp -r genesis/examples/hello-world ../my-document
cd ../my-document
# Install dependencies
npm install
# Run tests
npm test
# Start development
# Open assistant/index.html or validator/index.html in browsermy-project/
├── assistant/ # Document creation workflow
│ ├── index.html # Main assistant app
│ ├── css/styles.css # Custom styles
│ ├── js/
│ │ ├── app.js # Application logic
│ │ ├── workflow.js # 3-phase workflow
│ │ ├── prompts.js # AI prompts
│ │ └── core/ # Shared utilities (from assistant-core)
│ └── tests/ # Jest tests
├── validator/ # Document scoring
│ ├── index.html # Validator app
│ ├── js/
│ │ ├── app.js # Application logic
│ │ ├── validator.js # Scoring functions
│ │ └── core/ # Shared utilities (from validator-core)
│ └── tests/ # Jest tests
├── package.json # Dependencies
├── jest.config.js # Test configuration
├── eslint.config.js # Linting configuration
├── scripts/ # Setup/deploy scripts
└── .github/workflows/ # CI/CD
Common utilities for all assistants:
import { storage, workflow, ui } from './core/index.js';
// Save workflow state
await storage.saveProject({ id: 'project-1', name: 'My Document' });
// Get workflow phase
const phase = workflow.getCurrentPhase();
// Show toast notification
ui.showToast('Saved!', 'success');Common utilities for all validators:
import { storage, ui, copyToClipboard } from './core/index.js';
// Save validation history
await storage.saveValidation({ score: 85, timestamp: Date.now() });
// Copy to clipboard
await copyToClipboard(documentText);Each project includes the core libraries as actual files (not symlinks), so CI is straightforward:
steps:
- uses: actions/checkout@v6
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version-file: '.nvmrc'
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Lint and test
run: |
npm run lint
npm run test:coverageSee .github/workflows/ci.yml for the full workflow.
npm test # Run all tests
npm run test:assistant # Assistant tests only
npm run test:validator # Validator tests only
npm run test:coverage # Coverage report
npm run lint # ESLintCoverage targets: ≥70% (enforced in jest.config.js)
Check consistency across all 9 genesis projects:
cd genesis/project-diff
node diff-projects.js --ci # Check all MUST_MATCH files
node find-orphans.js --ci # Find orphaned JS filesSee project-diff/README.md for full documentation.
| Document | Description |
|---|---|
| ARCHITECTURE.md | Paired model, symlinks, CI/CD patterns |
| genesis/START-HERE.md | AI assistant entry point |
| genesis/02-QUICK-START.md | Quick start guide |
| genesis/03-CUSTOMIZATION-GUIDE.md | Customization options |
| genesis/04-DEPLOYMENT-GUIDE.md | GitHub Pages deployment |
Industry context and research informing this project's development philosophy:
- International AI Safety Report 2026: Extended Summary for Policymakers: Comprehensive analysis of AI capabilities, risks, and governance
- Claude Opus 4.6 Announcement: Anthropic's latest model capabilities (Feb 2026)
- State of Health AI 2026: Bessemer Venture Partners on AI investment trends (55% of health tech funding now AI-focused)
MIT License - See LICENSE file for details.
For historical context only. Active development: https://github.com/bordenet/docforge-ai