Proof through use

One wisdom layer. Many high-stakes domains.

Policy and compliance are the clearest place to start. The same foundation works anywhere decisions need evidence and a history you can stand behind. Different domain packs. Same loop.

  • ISMS / ISO 27001 policies, risks, controls, evidence, exceptions, findings, corrective actions, audit history
  • AI Act Compliance AI systems, classifications, obligations, evaluations, oversight, incidents, change history
  • Policy Application laws, local policy, eligibility criteria, case evidence, decisions, appeals
  • Educational Methodology teaching methods, learning outcomes, course activities, assessments, evidence, feedback loops
  • Vendor Risk vendors, attestations, DPAs, access, reviews, obligations, third-party risks
  • Customer Commitments promises, account context, security asks, deadlines, contract evidence, renewal risk
  • Product Decisions roadmap rationale, tradeoffs, customer evidence, dependencies, superseded decisions
  • Engineering Operations ADRs, incidents, migrations, dependencies, runbooks, deprecations, corrective actions
Domain pack · ISMS

Security and compliance, kept honest.

An ISMS is a hard memory problem. Policies, controls, evidence, and audit history all need to stay traceable and current over years. If operational memory holds up here, it holds up in other high-stakes places too.

This is not a full GRC suite. It's proof that WiseWare can keep one high-stakes domain living, reviewable, and tied to its sources.

  • Policy what the company decided
  • Risk what could go wrong
  • Control what mitigates the risk
  • Evidence proof the control ran
  • Exception what was deliberately set aside
  • Check what rules pass or flag
Ask

What evidence supports quarterly access review this quarter?

Q2 access review was signed off by the CTO on 2026-04-03. Evidence is Q2-Access-Review.pdf, originating from Jira AC-128.

Cites CTL-12 Control · Quarterly access review EV-219 Q2-Access-Review.pdf AC-128 Jira · access review ticket
Exception · EXC-08
stale

Legacy SSH access for vendor Acme

expires
2026-04-30
owner
Platform
Policy · POL-11
superseded

Onboarding security baseline

replaced by
POL-17 (2026-03-02)
Ask

Which exceptions expire this month?

One exception expires in April 2026: EXC-08 (Legacy SSH access for vendor Acme, Platform-owned). Renewal or closure is required by 2026-04-30.

EXC-08's last review is 41 days old. Consider re-confirming before renewal.

Cites EXC-08 Legacy SSH access · Acme