@meta
  v: 1
  route: /charter
  generated: 2026-06-07T00:00:00Z
  ttl: 1h

@intent
  purpose:    The TechMages.org Charter — who we serve, who we are not, the dual-use stance, and how white-hat values are engineered into the tools rather than printed on a page.
  audience:   msp, security-pro, student, agent
  capability: read, evaluate

@state
  serves[3]{audience,note}:
    MSPs,"First by design — scoped, authorized, logged, provable action against client systems"
    Security professionals,Pentesters and red/blue/purple teams on authorized engagements
    Serious students,Training for the work by building the tool and reading the source
  not_for: people seeking to break into systems they have no authorization to touch
  values_in_engineering[6]{value,how}:
    authorization-first,The engagement gate — offensive modules inert until a scoped engagement is armed
    scope-is-real,A scope allowlist checks every target at run time; out-of-scope is refused and logged
    accountable,Every job and refusal writes an audit row; the kill switch reaches every queue
    provable,Signed Agent Attestation Records (Ed25519 / JCS / did:web) verify what the deck did without trusting it
    safe-by-default,Ships in SAFE mode; the AI operator cannot arm an engagement itself
    understandable,Build-your-own from a documented BOM; open source; no black boxes

@actions
  - id: view_human
    method: GET
    href: /charter.html
  - id: explore_warlock
    method: GET
    href: /warlock.html

@context
  > The Charter is the ethos, meant to be read before the code. Security tooling is dual-use — the capability is the capability — so TechMages does not pretend it can stop abuse. Its answer is accountability engineered into the tool: authorization is explicit, scope is enforced not suggested, everything is audited, records are cryptographically provable, there is always a kill switch, and radio emission gets the strictest gate. The line: use these tools only on systems you own or are authorized to test, and keep your records.

@nav
  self:      /charter.agent
  parents:   [/.agent]
  peers:     [/warlock.agent, /deck.agent, /deck-gui.agent, /projects.agent, /index.agent, /contribute.agent]