04 · Memory

Templates & the Client Core.

Every new project starts from the latest template, automatically. Every result is locked back into the Core with a write-back block. The Core, not the chat, is the memory.

Start a project

The latest template, every time.

The Client Core template has one source of truth in the repo. It is bundled into the initialize-project skill on every commit, so improvements to the template reach every future project with no manual copying.

Template in the repo
20-client-template. The single source.
Bundled on commit
Carried inside initialize-project, always current.
Run initialize-project
Pick or create the client. Set archetype, goal, inputs.
Filled Core files
Five files, ready to upload to the new Project.
What comes in

The five Client Core files.

Uploaded into the client's Project. The first thing every skill reads.

brand-pack.md

The brand

Colour, type, voice, archetype, rules. The source of truth for everything we make for them.

imagery-lockins.md

The look

Registered image and video styles, so the whole team stays consistent.

reference-packs.md

The references

Saved, reusable reference and moodboard packs.

decisions-log.md

The memory

Every meaningful decision, dated. The client's history.

legal-templates.md

The scaffolding

Swiss legal scaffolding for that client.

archetype

Set first

One tag that modulates how every skill renders for them. A bank is never a startup.

After a result

Lock it in. One block.

Every skill that changes client state ends with a Save to Client Core block. You paste it into the named Project file. That is what makes the next chat, today or months later, start warm and on brand.

Save to Client Core

File   brand-pack.md

Action   replace section "Visual tokens"

Content

Primary  #1A1A1A
Accent   #C8552B
Display  Funnel Display, 500
Body     Funnel Sans, 300
Radius   16px · Grid 12-col

How the lock works

  1. The skill detects what changed and writes the block.
  2. On claude.ai you open the Project, edit the named file, and paste.
  3. If a writable store is connected, this can be written for you. The Core file stays the source of truth.
  4. The newest saved version wins. The change and the why are logged in decisions-log.
Drift detection. If a result changes a locked value or contradicts a logged decision, the block is flagged CHANGE or CONFLICT, old to new, and asks you to confirm before overwriting. A full audit runs via client-core-sync.
Two stores, two directions

House syncs down. Client Cores are edited in place.

House Core

Repo is the truth

The confidential layer flows one way, from the repo to the House Project through the GitHub connector. Read-only. Edit in the repo, push, then Sync. Never edit a synced file in the Project.

Client Core

Project is the truth

Per-client files are edited in the Project. Skills write back into them with the Save to Client Core block. Confidential House content never enters a client Core.