Skip to content

docs: add the shared publication boundary block (v1) #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rabestro merged 1 commit into from
Sep 12, 2026
Merged

docs: add the shared publication boundary block (v1) #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
23 changes: 23 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,29 @@
- **Lint**: `ruff check .`
- **Start**: `python3 bot.py` (mints anonymous token and challenges sparring bot).

## Publication boundary

<!-- dc-shared:publication v3 — keep identical across Fortemate repositories -->

- Fortemate is open-core. Public by nature, in the public repositories: their source (engine rules
and search, feature definitions and extractors, bot templates, the play client and server), serving
contracts, mechanics, and the programme numbers already published in the project READMEs. Private
repositories (evaluation service, training pipelines, proprietary evaluators, house bots, analytics,
infrastructure) stay private in full; this rule governs what may be written into the public ones.
- Always private, wherever it is written: trained weights, opening books, labelled corpora, production
parameter **values** (search profiles, candidate limits, table sizes, blend weights, time budgets),
experiment **verdicts** (win rates, feature importance, cost ratios, negative results) and the names
of private repositories, artifacts and hosts.
- Before writing to a public repository — code, docs, scaladoc, commit messages, Issues, pull requests,
review replies — check the text against that list. Values and verdicts go to the private knowledge
base and are referenced from public text by page title only; examples use
placeholders such as `<candidate-limit>` instead of real values.
- The rule is forward-only (ADR 009): nothing already published is retracted and history is never
rewritten. When unsure whether something is a definition or a verdict, ask the owner before
publishing.

<!-- /dc-shared:publication -->

## Issue management
<!-- dc-shared:issue-management v7 — keep identical across Fortemate repositories -->

Expand Down