Shipped Cognis
Meeting Visibility, Git-Truth Alignment, and Independent Link Verification
Cognis reads only the meetings a viewer is allowed to see. Execution alignment counts real git activity and reconciles with the cards. Link attribution is verified by a second, independent model.
Shipped since June 5.
Meeting visibility
- Meeting scope is classified at ingest. External and one-to-one meetings stay private. Organization ceremonies flow to the org.
- Cognis reads a meeting only when the viewer is allowed to see it.
- Memory facts are gated at read time, so a private meeting’s interpretive facts never surface org-wide.
- The scope verdict is persisted for audit.
- Teams channel and external meetings no longer auto-share.
- When retrieval returns nothing, Cognis says so instead of naming meetings, decisions, or action items it did not retrieve.
Alignment in git truth
- The Execution headline counts real git activity: commits, pull requests, meetings, documents.
- The headline and the per-initiative cards reconcile to the same totals.
- Link ratios stay within range instead of exceeding 100%.
- The Alignment Score card explains what counts as an activity.
Independent link verification
- Link attribution is now adjudicated by a second, independent model, separate from the one that proposed it.
- Merge commits are retired from the verified queue.
- Settled commits drop their stale suggestions.
- Explicit and manual links survive the daily lifecycle cleanup, even outside an initiative’s date window.
Grounded answers
- Cognis always returns a finalized, grounded answer, including for multi-step questions on large orgs.
- A reasoning error is never stored as an answer. Scheduled agent runs fail closed instead of persisting an apology as content.
- Cognis lists only what a tool returned this turn, and reports an empty result plainly.
Agent-first API access
- Link-proposal read and write endpoints are scope-gated, so a least-privilege API key is the full authority contract for an autonomous agent.
- The API-key scope picker covers agent and settings scopes.
Release
- Backend, frontend, and the model layer. Window since the June 5 release.
- 25+ merged pull requests.
- Database changes are additive: four new changesets.
- Deployed to production June 12.
Turn Your Releases Into Artifacts
Connect GitHub, generate release notes from real evidence, and keep every shipped change traceable.