Summary: The agent-contract for this wiki. Read this before reading or writing any page. Sources: initial architecture design, 2026-05-15; folder map and page types aligned with the vault on 2026-11-09 Last updated: 2026-11-09
STRUCTURE.md: 7Mind Company Wiki
This file is the single source of truth for how this wiki is organized and how agents should interact with it. Every agent that reads or writes to this wiki must read this file first.
1. Purpose
This wiki is the shared “second brain” for 7Mind’s engineering system. It gives AI agents (Claude Code instances running inside individual repos) the cross-repo context they cannot derive from a single codebase alone.
Primary readers: AI agents running in 7Mind repos. Secondary readers: human engineers who need a quick orientation. Primary authors: AI agents, after significant changes to their repo. Reviewer: Nikolas Haag (human review, periodic).
The wiki complements code; it does not duplicate it. Never paste code here. Never paste PR descriptions here. The wiki captures what the code cannot explain on its own: how repos connect, why decisions were made, what the product is, and how the company operates.
2. Folder Map
All wiki content lives in content/ within the brain repo. When you clone the repo, the structure looks like this:
brain/ git repo root
├── README.md what the repo is, link to brain.6mind.de
├── CLAUDE.md agent instructions (Claude Code reads this automatically)
├── agent-kit/ not part of the wiki: onboarding prompts and the CLAUDE.md / AGENTS.md templates for 7Mind repos
├── content/ all wiki pages live here
│ ├── index.md home page of brain.6mind.de
│ ├── STRUCTURE.md this file, read it first
│ ├── log.md append-only log of structural wiki changes
│ ├── raw/ immutable source documents for ingestion
│ ├── assets/ images and static files
│ │
│ ├── business/ business intelligence layer
│ │ ├── product/ what 7Mind is, its markets, strategic direction
│ │ ├── brand/ visual identity, voice, tone
│ │ ├── customers/ B2C, B2B, B2B2C segment notes
│ │ └── processes/ internal workflows (release, bug triage)
│ │
│ └── tech/ technical intelligence layer
│ ├── repos/ one file per repo, the most agent-critical section
│ ├── concepts/ architectural patterns and service configurations that span repos
│ ├── integrations/ cross-repo data flows and connection patterns
│ ├── guides/ step-by-step runbooks (for example adding a new plan)
│ ├── infrastructure/ AWS via Gymondo, legacy GCP, Cloudflare, Terraform, CI/CD, test accounts
│ ├── legacy/ concept and integration pages of retired systems, kept for history
│ ├── packages/ one file per shared NPM package (none documented yet; create the folder with the first one)
│ └── <project>/ one folder per running project (e.g. react-native-migration/), with its own <project>-index.md
│
└── quartz/ Quartz SSG (builds brain.6mind.de, do not edit)
When you open the wiki in Obsidian, open the vault at brain/content/, not brain/.
Paths in wiki pages are always relative to the vault root (content/). A link like [[elixir-backend]] resolves to content/tech/repos/elixir-backend.md.
Where a page goes
| The page is about | Folder |
|---|---|
| One repository | tech/repos/. A retired repo keeps its note here with status: legacy, because other repos point to that path |
| A pattern, a service or a domain model that spans repos | tech/concepts/ |
| How two or more repos or services talk to each other | tech/integrations/ |
| How to do a task, step by step | tech/guides/ |
| Hosting, DNS, CI/CD, shared accounts | tech/infrastructure/ |
| A time-bound effort with several pages | tech/<project>/ |
| A concept or integration of a retired system | tech/legacy/ |
When a system is retired, move its concept and integration pages to tech/legacy/, add a short banner under the header fields that says what replaced it and since when, and mark the entry (legacy) in tech-index.md. Links keep working because they resolve by basename.
3. Frontmatter Schema
Every page begins with YAML frontmatter followed by three required header fields, then a horizontal rule, then content.
Required header fields (after frontmatter, before content)
**Summary**: one sentence describing this page
**Sources**: where the information came from
**Last updated**: YYYY-MM-DDFrontmatter by page type
Repo note (tech/repos/*.md):
---
type: repo-note
repo: <exact-github-repo-slug>
stack: [language, framework, ...]
owner-repo: <repo-slug>
last-updated: YYYY-MM-DD
tags: []
status: active # active | legacy | archived | experimental
# legacy = still running but superseded, being decommissioned
# archived = retired, nothing of it runs any more
---Concept note (tech/concepts/*.md, and concept pages in tech/legacy/):
---
type: concept-note
last-updated: YYYY-MM-DD
tags: []
---Integration note (tech/integrations/*.md, and integration pages in tech/legacy/):
---
type: integration-note
last-updated: YYYY-MM-DD
tags: []
---Guide (tech/guides/*.md):
---
type: guide
last-updated: YYYY-MM-DD
tags: [runbook]
---Package note (tech/packages/pkg-*.md):
---
type: package-note
package: @7mind/<package-name>
repo: <source-repo-slug>
owner-repo: <source-repo-slug>
last-updated: YYYY-MM-DD
tags: [npm, shared]
---Infrastructure note (tech/infrastructure/*.md):
---
type: infra-note
last-updated: YYYY-MM-DD
tags: [gcp | cloudflare | github-actions | terraform]
---Business note (business/**/*.md):
---
type: product | brand | customer | process
last-updated: YYYY-MM-DD
tags: []
---Project note (tech/<project>/*.md):
---
type: project-note
project: <project-folder-name>
last-updated: YYYY-MM-DD
tags: []
---Index file (*-index.md):
---
type: index
last-updated: YYYY-MM-DD
tags: [index]
---Pages of retired systems keep their type and add the tag legacy.
4. Naming Conventions
| Thing | Rule | Example |
|---|---|---|
| All files | lowercase-with-hyphens.md | elixir-backend.md |
| Repo notes | match GitHub repo slug exactly | api-contracts.md |
| Package notes | pkg-<npm-name>.md | pkg-design-tokens.md |
| Index files | <folder>-index.md | tech-index.md |
| Tags | lowercase, hyphenated | b2b2c, github-actions |
Basenames must be unique across the entire vault. Obsidian wiki-links resolve by basename only. If two files share a basename, links break silently. Check uniqueness before creating a new file.
5. Cross-Link Pattern
Always use [[basename]] syntax for internal links. Never use relative paths.
Good: See [[7mind-mobile-apps-monorepo]] for the mobile repo.
Bad: See [7mind-mobile-apps-monorepo](../tech/repos/7mind-mobile-apps-monorepo.md).When linking to a specific section: [[basename#section-heading|Section Heading]].
6. Agent Write Protocol
When to update the wiki
Update your repo note (tech/repos/<your-repo>.md) after merging a change that affects any of:
- The repo’s purpose or primary behavior
- Its stack (new major dependency, language change, framework upgrade)
- Its deployment target or pipeline
- Its external service dependencies
- Its integration points with other repos
Do NOT update after every commit. One wiki update per meaningful architectural or behavioral shift is the right cadence.
Check facts against the repo’s default branch on the remote (origin/main, origin/develop), not a local working tree, which may be behind or on a feature branch.
Which notes to update
- Your
owner-reponote (always). - Any
tech/integrations/note that describes a connection your change affects. - Any
tech/guides/page whose steps your change alters. - Any
tech/packages/note if you published or significantly changed a shared package.
Do not edit business layer notes unless you have been explicitly asked to by a human.
Commit message format
wiki: update <page-or-repo-slug>: <short reason>
wiki: add <page-slug>: <short reason>
Examples:
wiki: update elixir-backend: added Stripe webhook handler
wiki: update website-next-js: checkout hands off to app.7mind.de
Every push to main rebuilds and publishes brain.6mind.de through Cloudflare Pages.
Do not
- Create new top-level folders (
business/,tech/) without human approval. - Add secrets, tokens, passwords, or environment variable values.
- Paste raw code blocks; reference file paths instead.
- Duplicate information already in the codebase. Link to it.
- Use em dashes anywhere in any page.
7. Repo Note Template
Use this template for every new file in tech/repos/. Fill in what you know; leave sections as TBD if unknown.
---
type: repo-note
repo: <repo-slug>
stack: []
owner-repo: <repo-slug>
last-updated: YYYY-MM-DD
tags: []
status: active
---
**Summary**: <one sentence>
**Sources**: direct code inspection
**Last updated**: YYYY-MM-DD
---
## Purpose
What this repo does, what problem it solves, who uses it.
## Stack
Languages, frameworks, and major dependencies worth noting.
## Key Files / Entry Points
- `path/to/file` -- what it does
## Deployment
How and where this deploys. Staging vs production environment. GitHub Actions workflow name. Target (GCP service, Cloudflare Pages, etc.).
## Dependencies
**External services**: third-party APIs or SDKs this repo calls.
**Internal**: other repos or packages this consumes; use [[wiki-links]].
## Integration Points
What consumes this repo's output: other internal repos, CDN, mobile clients, etc.
## Conventions
Non-obvious patterns an agent should know before editing: naming rules, gotchas, required env vars, local setup quirks.
## Agent Change Log
Append one line after each significant change. Do not edit past entries.
Format: `YYYY-MM-DD -- what changed and why`