|
Download core/README.md from playn4/playnfrontierAI: direct link, hf CLI and curl.
- Browser
- Download file 4.18 kB
-
https://huggingface.co/playn4/playnfrontierAI/resolve/main/core/README.md
- Command line
-
hf download hf://playn4/playnfrontierAI/core/README.md
-
curl -L -o README.md https://huggingface.co/playn4/playnfrontierAI/resolve/main/core/README.md
4.18 kB
OMN β the memory system in this folder
One idea: facts are the truth, the card is the window, close-out is one command. The agent's native episodic memory (Mnemopi) is the fuzzy recall layer; these files are the precise truth layer. Canon wins on conflict.
The 3 rules
- Facts are the only prose. Edit
facts/,decisions/,watch.md,learnings.md,projects/,backlog.md,inbox.md. Never duplicate their content anywhere else β README is pointers, card.md is generated. - The card is the window.
card.mdis rendered bytools/build.shfrom frontmatter β never hand-edit it. If a fact is past itscheck:interval, the card showsβ STALE. - Close-out is one command.
tools/close.shβ engine health (optional) β check.sh β doctor.sh gates β drain inbox β rebuild card β briefing β git snapshot. Zero drift possible.
Rituals
- Open: read
core/card.mdβ pull a fact file or skill only if the task needs it. - Look-up protocol: card β topic match β open the fact/decision β
tools/recall.shor grep core/ β ask the human. Don't guess. - Capture (mid-session): change the owning fact / append a decision / append a
learning line.
check.shis the freshness gate; close-out regenerates the card. - Close:
tools/close.sh(~60s; needs git for the snapshot step). - Clean mode: memory never auto-loads β reading the card IS the explicit ask.
Layout
core/
βββ card.md # generated β the whole open ritual
βββ README.md # this file β pointers only
βββ facts/ # verified truth, SSoT β 4 files, β€60 lines each
β βββ protocols.md # the numbered operating rules (live from first boot)
β βββ hardware.md # CANDIDATE β verify your machine, then promote to live
β βββ engines.md # CANDIDATE β the serving matrix, fill from reality
β βββ frontier.md # CANDIDATE β parking lot for candidates under the adoption bar
βββ decisions/ # ADRs 0000+ β proposed β accepted β superseded
βββ watch.md # candidates & gates, one table
βββ learnings.md # append-only SUCCESS log, newest first
βββ sessions/ # one daily briefing file per day
βββ projects/ # active only; done β archive/
βββ backlog.md # open questions + pending work
βββ inbox.md # one file; drained by close.sh
βββ sky/ # the memory sky β the canon drawn as a night sky (tools/sky.sh)
βββ archive/ # tombstoned + history β move, never delete
βββ tools/
βββ build.sh # facts β card.md (no deps)
βββ check.sh # schema + staleness + dead links β the "live" gate
βββ doctor.sh # reality drift: dead paths, dead providers, role pins, served ids
βββ health.sh # served-model pulse (optional engine gate)
βββ close.sh # the whole close-out ritual + git auto-commit
βββ recall.sh # exact grep; Mnemopi is the fuzzy layer
βββ graph.sh # canon link-graph β graph.json (wiki-link + supersedes edges)
βββ sky.sh # regrow the memory sky (sky.template.html β sky/)
Add a fact domain by adding a file under facts/ with proper frontmatter β the card
picks it up on the next build. Start a feed/analyzer in a core/ subdirectory only when
a real need appears; reference it from this README so doctor.sh can guard it.
Status model
- Facts:
live(verified truth) βsuperseded/archived(tombstoned to archive/) Β·candidate(to be verified β never treat as truth) - Decisions:
proposedβacceptedβsuperseded - Projects:
activeΒ·doneΒ·parked
Conventions
- Frontmatter on every fact/decision/project:
title, status, updated, priority, check (facts only, e.g. 7d), summary (one line for the card), tags, related. - Cross-refs β wiki-links in double brackets β
check.shverifies they resolve. - Learnings are append-only lines, newest first.
- Retirement = move to
archive/, never delete (trash-principle, facts/protocols.md).