Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,8 @@ Conversation Mode:
## Goal Mode Orchestration
- Treat Goal mode as a persistent completion contract: state the outcome, evidence of success, constraints, and stopping conditions before long-running work.
- Follow the Codex Goals pattern from https://developers.openai.com/cookbook/examples/codex/using_goals_in_codex: keep the objective visible, verify progress from artifacts or tests, and choose the next useful action from evidence.
- Keep `plan.md` as the current plan and `notes.md` as the compact memory of actual progress, decisions, user preferences, and important facts to preserve across turns.
- The main goal orchestrator must write actual progress and important things to remember in `notes.md` whenever meaningful work is completed or priorities change.
- Keep `plan.md` as the current plan and `notes.md` as a concise record of durable decisions and dated validation evidence. Current architecture, privacy, curriculum, packaging, limitations, and roadmap are linked from `plan.md`; update those documents when behavior changes.
- Record meaningful validation results and unresolved acceptance limits in `notes.md`; avoid accumulating task-by-task construction logs or completed roadmap items.
- If another user or agent modifies `plan.md` midway, stay calm, reread it, adapt Goal mode to the updated plan, and continue from the newest valid intent instead of fighting the change.
- Keep all project documents concise. Prefer short bullets with concrete facts over long narrative.

Expand Down
7 changes: 5 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ Build a macOS `.app` bundle:

```bash
npm run build:app
open dist/FluentAI.app
open dist/mac-arm64/FluentAI.app # Apple Silicon; use the path reported by the build
```

The desktop app calls the same Python bridge/API as the CLI and web UI, so demo behavior stays consistent.
Expand Down Expand Up @@ -169,9 +169,12 @@ tests/ unittest suite for core, bridge, and web endpoints
data/progress.json demo learner memory
```

## Design and limitations

See [architecture and memory](docs/GAP_AND_DESIGN.md), [privacy controls](docs/ONBOARDING_HOME_DESIGN.md), [curriculum](docs/CURRICULUM_DESIGN.md), and [packaging](docs/PACKAGING_DESIGN.md). The [product direction](docs/FLUENTAI_LIMITLESS_IDEAL.md) separates implemented behavior from limitations and remaining work; [notes](notes.md) preserves historical validation and provenance.

## Roadmap

- Add spaced repetition scheduling.
- Add richer lesson packs for Hindi and French.
- Add stable browser-based voice regression tests with mocked Realtime events.
- Add camera-frame fixtures for vision-context tests.
372 changes: 16 additions & 356 deletions docs/CURRICULUM_DESIGN.md

Large diffs are not rendered by default.

Loading
Loading