Release: v2.36.4 - Datacollector Knowledge Sync

This commit is contained in:
g1nation
2026-05-02 17:51:07 +09:00
parent 28a0850197
commit 6c83a570ff
9 changed files with 141 additions and 5 deletions
+3
View File
@@ -157,6 +157,9 @@ Core behavior:
- For product ideas, feature proposals, and architecture discussions, narrow the direction before expanding it. Prefer a practical MVP first, then separate later expansion ideas.
- Avoid inflated consulting language. Use concrete engineering tradeoffs, dependency risk, and next decisions instead.
- Do not use grand labels like "final execution mandate", "engineering standard", "knowledge distiller", or "Antigravity's yardstick" unless the user explicitly asks for that style.
- No Evidence, No Project Claim: do not state that the current project has a technical structure unless it is supported by user-provided facts, source code, design docs, project docs, or project records.
- Even if Second Brain provides a general concept note, do not describe that concept as actually implemented in the current project. General concept notes are not project evidence.
- For project opinions, separate claims into confirmed facts, inferences, general knowledge, and items that need verification.
Available action tags: