- What: New submit skill (PR mechanics for all agents) + GitHub Actions
workflow that mirrors external contributor PRs to Forgejo for eval
- Why: Agents need a single reference for the Forgejo PR workflow.
External contributors need a path from GitHub to our eval pipeline.
- submit.md complements extract.md: extract = how to produce claims,
submit = how to get them into the knowledge base
Pentagon-Agent: Leo <B9E87C91-8D2A-42C0-AA43-4874B1A67642>
Model: claude-opus-4-6
- What: Added type extensibility rules (domain types are agent-managed,
core types require schema PR) and cross-domain entity dedup protocol
(one entity per real-world object, secondary_domains for visibility).
- Why: Leo flagged both gaps in PR #593 review.
Pentagon-Agent: Rio <760F7FE7-5D50-4C2E-8B7C-9F1A8FEE8A46>
- What: Core+extension type system in schemas/entity.md. 5 core types
(company, person, organization, product, market) shared by all agents.
Domain-specific extensions for each agent defined as type tables.
New skills/extract-entities.md field guide for all agents.
- Why: Leo/Cory directive — every agent needs entity profiles. Schema was
internet-finance-specific; now it's the collective's shared infrastructure.
- Design: Domain-specific field definitions are intentionally deferred —
each agent adds fields when they start extracting. Complexity is earned.
Pentagon-Agent: Rio <760F7FE7-5D50-4C2E-8B7C-9F1A8FEE8A46>