sgeboers
/
motief
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
71 Commits
1 Branch
0 Tags
6.0 MiB
 
 
 
Tag: Branch: Tree: c0d1c59bd7
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c0d1c59bd7'
${ noResults }
motief/.mindmodel
History
Sven Geboers 445f0bfb24
feat(ansible-example): add @ansible/example package, tests, CI, publish & deploy workflows, docs and changelog 		1 month ago
..
constraints feat(mindmodel): add manifest loader and tests 1 month ago
examples chore: add .mindmodel/ project constraints and conventions 1 month ago
patterns chore: add .mindmodel/ project constraints and conventions 1 month ago
README.md docs(mindmodel): add README and tooling note; chore(tooling): add minimal pre-commit 1 month ago
anti-patterns.yaml chore: add .mindmodel/ project constraints and conventions 1 month ago
architecture.yaml chore: add .mindmodel/ project constraints and conventions 1 month ago
conventions.yaml chore: add .mindmodel/ project constraints and conventions 1 month ago
dependencies.yaml chore: add .mindmodel/ project constraints and conventions 1 month ago
domain-glossary.yaml chore: add .mindmodel/ project constraints and conventions 1 month ago
manifest.yaml chore(mindmodel): add sanitized read-only manifest and reviewer README 1 month ago
stack.yaml chore: add .mindmodel/ project constraints and conventions 1 month ago
system.md feat(ansible-example): add @ansible/example package, tests, CI, publish & deploy workflows, docs and changelog 1 month ago

README.md

.mindmodel

This directory contains a generated, read-only snapshot of the repository's "mind model" — structured metadata and evidence used by tooling to reason about repository intent, patterns, and decisions.

Guidelines

  • Read-only: Treat files in this directory as generated artifacts. Local tooling or CI may regenerate or validate them; avoid manual edits unless you are intentionally updating the generator.
  • No secrets: Do not place any credentials, tokens, or sensitive data here. The validator that consumes this folder is designed to detect common secret patterns and will fail if secrets are found.
  • Safe to read: Tools and CI may read these files. They must avoid opening or parsing arbitrary repository secrets and should operate in read-only mode.
  • Validation: CI workflows will run a validator against this folder (if present) to ensure manifest shape, evidence snippets, and referenced files meet project rules.

If you need to propose a change to the mind model, open a PR describing the intent and the generator changes. The CI validator will validate the submitted artifact before merge.