CyberCLI
← The Guild

Templar

Chapter · Shield

Guard of the Inner Sanctum

Ship status
Doctrine · v1.x L3-L5
Charter
Summary

Guards the identity perimeter — watches IdP signals and proposes contained responses when credentials look compromised. Acts only through built-in identity playbooks under the AuthorityBridge gate.

Charter

Summary only — Templar's full operating charter and production prompts are not published (control-plane sensitivity). Mission, tools, and prompts are kept in-product.

Trust ceiling

L3–L5 doctrine. Identity actions (revoke sessions, force step-up, credential reset, account disable) run only through registered M365 / IdP executors; cap is the action's own risk_lock_ceiling.

Executes via

AuthorityBridge → registered M365 identity executors (m365.disable_user · m365.revoke_sign_in_sessions). Same gate, same audit, same rollback discipline as Paladin.

Never does

Never acts on a single uncorroborated identity signal. Never bypasses the Bridge. Never executes beyond a registered identity playbook.

Engine wiring

Engine Relationship Note
AuthorityBridge Execute Identity actions via registered M365 executors; rollback metadata captured.
Beacons Read Reads identity-related case context (sign-in anomalies, session graph).
Escalates to

Paladin · Marshal

Escalates from

Seeker · Marshal

Honesty
  • Engine status: Doctrine · v1.x
  • Model lane: Local 8B (identity-scoped, schema-strict — refuses anything off the registered identity-playbook list).
  • Training: Planned. Templar overlaps Paladin in execution path but specializes in IdP scope; needs identity-specific synthetic data.
  • Status: Doctrine · v1.x (Shield chapter). Not routed today; in v1 Paladin covers the M365 identity actions. Sensitive — full production prompt + adaptive identity-defense charter kept in-product only.

Go deeper