recall-os 0.1.0

package/examples/generated-nextjs/docs/00-product/BRD.md

@@ -0,0 +1,9 @@
+# BRD: generated-nextjs
+
+## Purpose
+
+Describe the business goal, target users, and success criteria for this repository.
+
+## Current Status
+
+Draft.

package/examples/generated-nextjs/docs/00-product/PRD.md

@@ -0,0 +1,13 @@
+# PRD: generated-nextjs
+
+## Purpose
+
+Describe what this repository is building and why.
+
+## Current Status
+
+Draft.
+
+## Notes
+
+Keep product intent durable here. Do not rely on chat history as source of truth.

package/examples/generated-nextjs/docs/10-architecture/ARCHITECTURE.md

@@ -0,0 +1,11 @@
+# Architecture
+
+## Purpose
+
+Describe the accepted architecture for this repository.
+
+## Current Status
+
+No architecture decisions are accepted yet.
+
+Use ADRs to accept architecture choices.

package/examples/generated-nextjs/docs/10-architecture/FILE_WRITE_POLICY.md

@@ -0,0 +1,8 @@
+# File Write Policy
+
+Default behavior:
+
+- Skip existing files.
+- Use dry run before risky writes.
+- Require explicit force to overwrite.
+- Never write outside the repository root.

package/examples/generated-nextjs/docs/10-architecture/MEMORY_ENGINE.md

@@ -0,0 +1,16 @@
+# Repository Memory
+
+Repository memory is the durable source of truth for humans and AI agents.
+
+Source-of-truth order:
+
+1. Accepted ADRs and repository decisions
+2. Architecture docs
+3. Engineering standards
+4. Current PRD and accepted change requests
+5. Security and testing docs
+6. Module docs
+7. Feature plans
+8. Task files
+9. External context
+10. Chat history

package/examples/generated-nextjs/docs/20-security/SECURITY_MODEL.md

@@ -0,0 +1,11 @@
+# Security Model
+
+## Current Status
+
+Draft.
+
+## Baseline Rules
+
+- Do not commit secrets.
+- Do not read or copy `.env` files into docs.
+- Do not add network, telemetry, cloud, MCP runtime, or AI API behavior without explicit review.

package/examples/generated-nextjs/docs/20-security/THREAT_MODEL.md

@@ -0,0 +1,7 @@
+# Threat Model
+
+## Current Status
+
+Draft.
+
+Track repository-specific risks here as the project evolves.

package/examples/generated-nextjs/docs/30-modules/README.md

@@ -0,0 +1,17 @@
+# Module Memory
+
+Module memory records what each important module owns, how it should be tested, and which decisions
+affect it.
+
+Future module folders should use:
+
+```txt
+docs/30-modules/<module>/
+  MODULE.md
+  TASKS.md
+  TEST_PLAN.md
+  DECISIONS.md
+```
+
+Agents should update module memory when implementation changes responsibilities, boundaries, tests,
+risks, or decisions.

package/examples/generated-nextjs/docs/40-features/README.md

@@ -0,0 +1,22 @@
+# Feature Memory
+
+Feature memory records requirements, acceptance criteria, plans, tests, reviews, and completion
+evidence.
+
+Future feature folders should use:
+
+```txt
+docs/40-features/F-###-<feature>/
+  PRD.md
+  ACCEPTANCE.md
+  ARCHITECTURE_IMPACT.md
+  CHANGE_REQUESTS.md
+  PLAN.md
+  TASKS.md
+  TEST_PLAN.md
+  REVIEW.md
+  COMPLETION_REPORT.md
+```
+
+Agents should not implement meaningful feature work without a feature plan or clear source-of-truth
+reference.

package/examples/generated-nextjs/docs/50-quality/QUALITY_GATES.md

@@ -0,0 +1,11 @@
+# Quality Gates
+
+Do not claim completion without evidence.
+
+Completion evidence should include:
+
+- Files changed.
+- Tests run.
+- Results.
+- Skipped checks.
+- Remaining risks.

package/examples/generated-nextjs/docs/50-quality/TESTING_STRATEGY.md

@@ -0,0 +1,5 @@
+# Testing Strategy
+
+Tests should derive from acceptance criteria, risk, security invariants, and module boundaries.
+
+Document required unit, integration, security, and golden tests as the repository grows.

package/examples/generated-nextjs/docs/60-engineering/AI_AGENT_RULES.md

@@ -0,0 +1,6 @@
+# AI Agent Rules
+
+AI agents must follow repository memory over model preference.
+
+If a request conflicts with accepted repository memory or engineering standards, stop and report the
+conflict.

package/examples/generated-nextjs/docs/60-engineering/ENGINEERING_STANDARDS.md

@@ -0,0 +1,11 @@
+# Engineering Standards
+
+Repository rules override model preferences.
+
+Baseline rules:
+
+- Never commit secrets.
+- Keep changes scoped.
+- Update docs when behavior or architecture changes.
+- Add tests or document why tests were skipped.
+- Do not claim completion without evidence.

package/examples/generated-nextjs/docs/adrs/README.md

@@ -0,0 +1,5 @@
+# Architecture Decision Records
+
+Accepted architecture choices belong here.
+
+Presets and AI agents may propose decisions, but humans accept them.

package/examples/generated-nextjs/docs/adrs/proposed/ADR-PROPOSED-nextjs-data-layer.md

@@ -0,0 +1,23 @@
+# Proposed ADR: Use a typed data layer with PostgreSQL
+
+## Status
+
+Proposed
+
+## Context
+
+The app needs a database and a typed access layer.
+
+## Decision
+
+Consider Drizzle or Prisma with PostgreSQL, awaiting human acceptance.
+
+## Alternatives Considered
+
+- A hosted backend or BaaS.
+- Raw SQL.
+
+## Consequences
+
+- Type-safe queries and migrations.
+- Adds an ORM and schema workflow.

package/examples/generated-nextjs/docs/adrs/proposed/ADR-PROPOSED-nextjs-framework.md

@@ -0,0 +1,24 @@
+# Proposed ADR: Use Next.js
+
+## Status
+
+Proposed
+
+## Context
+
+The team needs a React framework for a production web application.
+
+## Decision
+
+Consider Next.js as the application framework. This is not accepted until a human reviews and
+accepts it.
+
+## Alternatives Considered
+
+- A Vite single-page app with a separate API.
+- Remix or another framework.
+
+## Consequences
+
+- Server rendering, routing, and a large ecosystem.
+- Couples the app to Next.js conventions.

package/examples/generated-nextjs/docs/adrs/proposed/ADR-PROPOSED-nextjs-routing-app-router.md

@@ -0,0 +1,23 @@
+# Proposed ADR: Use the App Router
+
+## Status
+
+Proposed
+
+## Context
+
+Next.js offers the App Router and the legacy Pages Router.
+
+## Decision
+
+Consider the App Router with Server Components, awaiting human acceptance.
+
+## Alternatives Considered
+
+- The Pages Router.
+- A mix during migration.
+
+## Consequences
+
+- Server Components and nested layouts.
+- Requires understanding server and client boundaries.

package/examples/generated-nextjs/docs/adrs/proposed/ADR-PROPOSED-nextjs-styling-tailwind.md

@@ -0,0 +1,23 @@
+# Proposed ADR: Use Tailwind CSS
+
+## Status
+
+Proposed
+
+## Context
+
+The app needs a styling approach.
+
+## Decision
+
+Consider Tailwind CSS for styling, awaiting human acceptance.
+
+## Alternatives Considered
+
+- CSS Modules.
+- A component library with its own styling.
+
+## Consequences
+
+- Fast, consistent utility-based styling.
+- Markup includes utility classes that teams must standardize.

package/examples/generated-nextjs/docs/adrs/proposed/ADR-PROPOSED-nextjs-testing.md

@@ -0,0 +1,23 @@
+# Proposed ADR: Use Vitest and Playwright
+
+## Status
+
+Proposed
+
+## Context
+
+The app needs unit, component, and end-to-end testing.
+
+## Decision
+
+Consider Vitest with Testing Library and Playwright, awaiting human acceptance.
+
+## Alternatives Considered
+
+- Jest.
+- Cypress for end-to-end tests.
+
+## Consequences
+
+- Fast unit and component tests plus reliable end-to-end coverage.
+- Teams maintain two test toolchains.

package/examples/generated-nextjs/docs/ai/AI_AGENTS_SKILLS_MCP_STRATEGY.md

@@ -0,0 +1,7 @@
+# AI Agents, Skills, And MCP Strategy
+
+Root agent files are entry points, not guarantees.
+
+Durable memory lives in `docs/`.
+
+MCP is optional external context and does not override accepted repository memory.

package/examples/generated-nextjs/docs/ai/MCP_STRATEGY.md

@@ -0,0 +1,6 @@
+# MCP Strategy
+
+MCP is not required for this repository.
+
+If MCP is introduced later, document trusted servers, data accessed, permissions, risks, and
+source-of-truth rules.

package/examples/generated-nextjs/docs/ai/RECALL_COMMANDS.md

@@ -0,0 +1,133 @@
+# Recall OS Commands
+
+This document records the Recall OS commands available to humans and AI agents.
+
+## Completion Gate
+
+Before claiming implementation work is complete, run:
+
+```txt
+pnpm test:run
+pnpm typecheck
+recall doctor
+```
+
+If `recall doctor` reports errors, fix them or report why they cannot be fixed. If it reports
+warnings, address them or record why they are acceptable.
+
+Package binary behavior is covered by binary integration tests.
+
+## Commands
+
+### `recall init`
+
+Initialize neutral repository memory.
+
+Options:
+
+- `--preset <id>`: apply optional preset guidance and proposed decisions.
+- `--dry-run`: show planned writes without writing files.
+- `--force`: overwrite existing files explicitly.
+- `--reinit`: required with `--force` to overwrite an existing Recall OS installation (a directory
+  that already has `.recall/config.json`). Without it, `--force` refuses, protecting existing
+  repository memory.
+
+Init also generates a tracked pre-commit hook at `.recall/hooks/pre-commit` that runs
+`recall doctor` plus any `preCommitGates` in `.recall/config.json`. Init proposes, but does not run,
+the activation command `git config core.hooksPath .recall/hooks`.
+
+### `recall adopt`
+
+Inspect an existing repository through read-only manifest and marker files, then write a proposed
+adoption report and proposed framework ADRs for human review. Adopt never executes repository code
+and never produces accepted memory.
+
+Options:
+
+- `--dry-run`: show planned writes without writing files.
+- `--force`: overwrite existing files explicitly.
+
+### `recall skill create <name>`
+
+Generate a portable AI agent skill as `SKILL.md` for both Claude Code (`.claude/skills/`) and the
+portable Agent Skills target (`.agents/skills/`). Known names use the built-in catalog; unknown
+names produce a valid skeleton. Generated skills contain no scripts.
+
+Options:
+
+- `--dry-run`: show planned writes without writing files.
+- `--force`: overwrite existing files explicitly.
+
+### `recall skill list`
+
+List the built-in catalog skills.
+
+### `recall mcp add <server>`
+
+Generate offline, proposed memory for an MCP server (for example `figma`) as
+`docs/ai/mcp/<server>.md` plus a proposed adoption ADR. Recall OS never connects to the MCP server
+or makes network calls; the agent records durable MCP-derived context into the generated memory for
+human review. It also installs a `capture-mcp-context` agent skill that prompts the agent to record
+that context.
+
+Options:
+
+- `--dry-run`: show planned writes without writing files.
+- `--force`: overwrite existing files explicitly.
+
+### `recall preset list`
+
+List built-in presets.
+
+### `recall feature create <name>`
+
+Create feature memory docs under the configured features directory.
+
+Options:
+
+- `--dry-run`: show planned writes without writing files.
+- `--force`: overwrite existing files explicitly.
+
+### `recall adr create <title>`
+
+Create a proposed ADR under the configured ADR directory.
+
+Options:
+
+- `--dry-run`: show planned writes without writing files.
+- `--force`: overwrite existing files explicitly.
+
+### `recall adr accept <name>`
+
+Promote a proposed ADR to accepted repository memory. A proposal under
+`docs/adrs/proposed/ADR-PROPOSED-<slug>.md` becomes a numbered, accepted `ADR-####-<slug>.md` and
+the proposal is removed; an existing numbered Proposed ADR is accepted in place.
+
+Options:
+
+- `--dry-run`: show planned writes without writing files.
+- `--force`: overwrite existing files explicitly.
+
+### `recall module create <name>`
+
+Create module memory docs under the configured modules directory.
+
+Options:
+
+- `--dry-run`: show planned writes without writing files.
+- `--force`: overwrite existing files explicitly.
+
+### `recall doctor`
+
+Check whether repository memory is structurally healthy enough for AI-assisted work, whether basic
+engineering evidence is present, and whether memory references decisions that exist and are
+accepted.
+
+Doctor also runs deterministic drift checks: feature or module memory that references a missing ADR
+is an error, and memory that references a not-yet-accepted ADR is a warning.
+
+Exit codes:
+
+- `0`: healthy
+- `1`: warnings only
+- `2`: errors

package/examples/generated-nextjs/docs/ai/presets/nextjs-guidance.md

@@ -0,0 +1,30 @@
+# Next.js Preset Guidance
+
+This is proposed guidance, not accepted. Convert any architecture choice into a proposed ADR, then
+an accepted ADR, before treating it as repository truth.
+
+## Decision forks this stack forces
+
+- Routing: App Router vs Pages Router.
+- Rendering: Server Components and server actions vs client-heavy rendering.
+- Data layer: Drizzle or Prisma with PostgreSQL vs a hosted backend.
+- Styling: Tailwind CSS vs CSS Modules vs a component library.
+- Testing: Vitest with Testing Library and Playwright vs other runners.
+
+## Recommended structure (proposed)
+
+- The App Router with route groups and colocated server components.
+- A typed data layer isolated from UI components.
+- Shared UI primitives and a consistent styling system.
+
+## Testing (proposed)
+
+- Unit and component tests with Vitest and Testing Library.
+- End-to-end tests with Playwright for critical flows.
+- Type-safe data access tested against a disposable database.
+
+## Security considerations (proposed)
+
+- Keep secrets in server-only environment variables, never in client bundles.
+- Validate input on the server, including server actions and route handlers.
+- Scope authentication and authorization on the server, not the client.

package/examples/generated-python-fastapi/.recall/config.json

@@ -0,0 +1,17 @@
+{
+  "version": "0.1.0",
+  "templateVersion": "0.1.0",
+  "preset": "python-fastapi",
+  "memoryProfile": "standard",
+  "mode": "standard",
+  "aiTools": [
+    "claude",
+    "codex"
+  ],
+  "docsDir": "docs",
+  "featuresDir": "docs/40-features",
+  "modulesDir": "docs/30-modules",
+  "adrDir": "docs/adrs",
+  "writePolicy": "skip-existing",
+  "preCommitGates": []
+}

package/examples/generated-python-fastapi/.recall/hooks/pre-commit

@@ -0,0 +1,9 @@
+#!/bin/sh
+# Recall OS pre-commit hook.
+# Generated by `recall init`. Edit gates in .recall/config.json (preCommitGates),
+# then re-run `recall init --force` to regenerate this hook.
+# Enable once per clone with:
+#   git config core.hooksPath .recall/hooks
+set -e
+
+recall doctor

package/examples/generated-python-fastapi/AGENTS.md

@@ -0,0 +1,15 @@
+# generated-python-fastapi Agent Instructions
+
+This repository uses Recall OS repository memory.
+
+Start with durable source-of-truth docs under `docs/`.
+
+Required reading:
+
+- `docs/00-product/PRD.md`
+- `docs/10-architecture/ARCHITECTURE.md`
+- `docs/20-security/SECURITY_MODEL.md`
+- `docs/50-quality/QUALITY_GATES.md`
+- `docs/60-engineering/ENGINEERING_STANDARDS.md`
+
+Repository rules override model preferences. If instructions conflict, stop and report the conflict.

package/examples/generated-python-fastapi/CLAUDE.md

@@ -0,0 +1,7 @@
+# generated-python-fastapi Claude Instructions
+
+Use this file as a short routing guide.
+
+The durable project memory lives in `docs/`. Do not rely on chat history as source of truth.
+
+Read `AGENTS.md` and the relevant docs before changing code or repository memory.

package/examples/generated-python-fastapi/README.md

@@ -0,0 +1,11 @@
+# Python FastAPI Example
+
+This folder shows the repository memory generated by:
+
+```bash
+recall init --preset python-fastapi
+```
+
+The Python FastAPI preset adds opinionated, proposed guidance and proposed ADRs for the stack's real
+decision forks (framework, database and migrations, validation, testing, and caching). It does not
+create application code or silently accept architecture choices.

package/examples/generated-python-fastapi/docs/00-product/BRD.md

@@ -0,0 +1,9 @@
+# BRD: generated-python-fastapi
+
+## Purpose
+
+Describe the business goal, target users, and success criteria for this repository.
+
+## Current Status
+
+Draft.

package/examples/generated-python-fastapi/docs/00-product/PRD.md

@@ -0,0 +1,13 @@
+# PRD: generated-python-fastapi
+
+## Purpose
+
+Describe what this repository is building and why.
+
+## Current Status
+
+Draft.
+
+## Notes
+
+Keep product intent durable here. Do not rely on chat history as source of truth.

package/examples/generated-python-fastapi/docs/10-architecture/ARCHITECTURE.md

@@ -0,0 +1,11 @@
+# Architecture
+
+## Purpose
+
+Describe the accepted architecture for this repository.
+
+## Current Status
+
+No architecture decisions are accepted yet.
+
+Use ADRs to accept architecture choices.

package/examples/generated-python-fastapi/docs/10-architecture/FILE_WRITE_POLICY.md

@@ -0,0 +1,8 @@
+# File Write Policy
+
+Default behavior:
+
+- Skip existing files.
+- Use dry run before risky writes.
+- Require explicit force to overwrite.
+- Never write outside the repository root.

package/examples/generated-python-fastapi/docs/10-architecture/MEMORY_ENGINE.md

@@ -0,0 +1,16 @@
+# Repository Memory
+
+Repository memory is the durable source of truth for humans and AI agents.
+
+Source-of-truth order:
+
+1. Accepted ADRs and repository decisions
+2. Architecture docs
+3. Engineering standards
+4. Current PRD and accepted change requests
+5. Security and testing docs
+6. Module docs
+7. Feature plans
+8. Task files
+9. External context
+10. Chat history

package/examples/generated-python-fastapi/docs/20-security/SECURITY_MODEL.md

@@ -0,0 +1,11 @@
+# Security Model
+
+## Current Status
+
+Draft.
+
+## Baseline Rules
+
+- Do not commit secrets.
+- Do not read or copy `.env` files into docs.
+- Do not add network, telemetry, cloud, MCP runtime, or AI API behavior without explicit review.

package/examples/generated-python-fastapi/docs/20-security/THREAT_MODEL.md

@@ -0,0 +1,7 @@
+# Threat Model
+
+## Current Status
+
+Draft.
+
+Track repository-specific risks here as the project evolves.

package/examples/generated-python-fastapi/docs/30-modules/README.md

@@ -0,0 +1,17 @@
+# Module Memory
+
+Module memory records what each important module owns, how it should be tested, and which decisions
+affect it.
+
+Future module folders should use:
+
+```txt
+docs/30-modules/<module>/
+  MODULE.md
+  TASKS.md
+  TEST_PLAN.md
+  DECISIONS.md
+```
+
+Agents should update module memory when implementation changes responsibilities, boundaries, tests,
+risks, or decisions.

package/examples/generated-python-fastapi/docs/40-features/README.md

@@ -0,0 +1,22 @@
+# Feature Memory
+
+Feature memory records requirements, acceptance criteria, plans, tests, reviews, and completion
+evidence.
+
+Future feature folders should use:
+
+```txt
+docs/40-features/F-###-<feature>/
+  PRD.md
+  ACCEPTANCE.md
+  ARCHITECTURE_IMPACT.md
+  CHANGE_REQUESTS.md
+  PLAN.md
+  TASKS.md
+  TEST_PLAN.md
+  REVIEW.md
+  COMPLETION_REPORT.md
+```
+
+Agents should not implement meaningful feature work without a feature plan or clear source-of-truth
+reference.