Everything is a node
Claims, determinations, parcels, heritage sites, people, organisations, agreements, systems and documents live as typed, classified records.
Sovereign Knowledge Graph · Australian ISM Discipline · CARE & FAIR Controls
BlakSmith is an open, self-hosted knowledge graph built for protected Indigenous land title, cultural heritage and sensitive enterprise information, where custodians control the keys and rules rather than the platform operator. Paired with our vendor-neutral Indigenous Data Governance (IDG) Control Catalogue, it turns CARE, FAIR and Maiam nayri Wingara principles into 68 measurable controls in the discipline of the Australian Information Security Manual (ISM).
1 · What BlakSmith Is & Why It Is Used
Organisations holding native title claims, Indigenous Land Use Agreements (ILUAs), cultural heritage records, tenure histories or sensitive corporate data usually scatter them across shared drives, spreadsheets and SaaS tools where administrators can read anything and provenance disappears on the first export. BlakSmith brings those records into one versioned, auditable knowledge graph governed by explicit cultural protocols and measurable CARE & FAIR controls.
Claims, determinations, parcels, heritage sites, people, organisations, agreements, systems and documents live as typed, classified records.
Custodian authority, consultation obligations, tenure overlaps, system dependencies and data lineage are explicit and deterministically queryable.
Reads, refusals, consent changes, exports and key actions append to a SHA-256 hash-chained log with full temporal (“as-of”) reconstruction.
Access, encryption, presentation, sharing and AI use are enforced centrally before data leaves storage, never left to convention.
Custodian authority is evaluated before clearance. Tenant owners, system admins, API keys, AI agents and emergency break-glass claims are refused access to protocol-bound material.
Sensitive properties are sealed with AES-256-GCM envelope encryption before reaching Postgres (including version snapshots). Communities can hold their own key and erase data cryptographically.
Geometries are generalised to community-chosen grid cells, coordinate-shaped properties are stripped from packages, deceased-person names are suppressed, and restricted records fail closed.
Consent is collective, purpose-bound and revocable. Derived datasets carry no inherited consent, and protocol-bound or restricted records are excluded from embeddings and external AI models.
PostgreSQL row-level security isolates every tenant at the database layer, while an append-only SHA-256 hash chain lets communities verify access logs offline against anchored digests.
Licensed under Apache-2.0 and built for onshore Australian deployment via API, web UI and MCP. AI explains deterministic graph relationships; it never invents them or decides cultural sensitivity.
2 · The Core Governance Shift
Most enterprise systems answer only one question: how harmful would a leak be? They attach a classification label, lock the record behind an administrator role, and quietly hand authority over community knowledge to whoever operates the system. IDG separates two distinct questions and assigns authority differently.
Answered by an ordered sensitivity ladder (public through
restricted) that drives encryption, network transport, vetting, logging and
secure environments. Automated pipelines may raise a classification, never lower it.
Answered by cultural protocols, Local Contexts labels and nominated community custodian groups. No system role, tenant owner, administrator or emergency break-glass claim can override community authority over protocol-bound material.
3 · CARE & FAIR Data Handling Lifecycle
Select any lifecycle stage below (use mouse, touch, or Left/Right arrow keys) to inspect its proposed controls, CARE and FAIR alignment, and operational KPIs. Every control ID links directly to its full ISM-style specification in the manual.
Lifecycle Stage 1 of 8
Establish community authority above organisational oversight, embed Aboriginal and Torres Strait Islander participation in data governance bodies, define separation of duties, and capture community data priorities and capability support needs before collection begins.
KPI-LC1 Datasets with nominated community authority(Datasets with named community authority / Total Indigenous datasets) x 100%
KPI-LC1b Community data priorities actioned & reported(Documented priorities reviewed & reported on schedule / Total recorded priorities) x 100%
Lifecycle Stage 2 of 8
Obtain and record free, prior and informed consent (FPIC) collectively before ingesting or creating data, uphold the right to decline, vary or withdraw consent, suspend processing immediately when new information arises, and review data stewardship and quality with the community.
KPI-LC2 Ingestion batches gated by valid collective FPIC(Ingested Indigenous batches with valid FPIC record / Total batches) x 100%
KPI-LC2b Consent withdrawal / new-information suspension latencyTime from recorded withdrawal or new-info flag to access refusal
Lifecycle Stage 3 of 8
Attach ordered sensitivity classifications that automated systems can only raise, bind cultural protocols and Local Contexts TK/BC labels directly to every record so they travel across copies and derivatives, fail closed on existence hiding for restricted records, and maintain protocol-aware FAIR metadata.
KPI-LC3 Classified & protocol-labelled record completeness(Records with valid classification + applicable protocols/labels / Total records) x 100%
KPI-LC3b Existence-hiding leak rate across read pathsDetected leaks of hidden records across search, counts, maps, APIs and errors
Lifecycle Stage 4 of 8
Protect sensitive data at rest with application-level envelope encryption and in transit with verified TLS, isolate tenants at the database engine layer, keep data onshore by default, disclose sub-processors, match recipient environments to data sensitivity, and offer key custody up to community-held keys.
KPI-LC4 Sensitive payloads sealed with per-custodian-group keys(Sensitive+ payloads envelope-encrypted under group/tenant key / Total sensitive+ payloads) x 100%
KPI-LC4b Onshore residency & sub-processor disclosure complianceUnapproved cross-border deployments or undisclosed sub-processors
Lifecycle Stage 5 of 8
Prevent operator roles and break-glass accounts from overriding cultural protocols, require strong MFA and step-up authentication, gate joiner/mover/leaver access on vetting and cultural competency training, enforce purpose limitation, require fresh approval for secondary uses and derivatives, supply disaggregated data on community request, and ban unauthorised AI training or prompting.
KPI-LC5 Protocol-bound operator override refusal rate(Refused operator/break-glass/AI attempts on protocol-bound data / Total attempts) x 100%
KPI-LC5b Same-day leaver/revocation removal & training currency(Access removed <= 24h & active users with current cultural training / Total) x 100%
Lifecycle Stage 7 of 8
Enforce agreement-bound retention limits with verified purges across primary stores and backups, enable communities to repatriate data in usable formats with protocols intact, support cryptographic erasure per custodian group, require signed destruction attestations, and notify communities promptly of any breach or cultural harm.
KPI-LC7 Timely destruction & signed attestation completion(Expired/withdrawn datasets destroyed with signed attestation / Total due) x 100%
KPI-LC7b Community breach notification SLA adherence(Incidents notified within agreement SLA or <= 72h & never after regulators / Total) x 100%
Lifecycle Stage 8 of 8
Operate a tamper-evident hash-chained audit log that communities can independently verify, perform independent access audits, maintain protocol-aware community data inventories, run scheduled CARE/FAIR self-assessments with community review, anchor signed automated evidence bundles to the audit chain, verify transfer logs and backup restore drills, and commission impartial partnership health checks.
KPI-LC8 IDG Domain & Overall Maturity Level (IDG-ML0 to ML3)Domain = min(applicable controls); Overall = min(applicable domains)
KPI-LC8b Automated evidence pass rate & audit chain integrity(Passing mapped checks / Total mapped checks) x 100% with 0 chain breaks
Where a community protocol requires it, unauthorised people cannot learn a restricted record exists in search, counts, maps or error messages (IDG-TEC-003).
Communities can purge data and destroy per-group encryption keys on withdrawal or expiry; only the signed destruction attestation remains (IDG-TEC-007, IDG-TEC-016).
Consent never launders into derived outputs or AI models. Every secondary use and derived dataset requires fresh community approval (IDG-PRC-004, IDG-TEC-017).
4 · Built for Two Audiences
The framework is written in plain Australian English so communities can hold data holders to account and consuming entities know exactly what must be in place before and after receiving Indigenous data.
Plain-language clarity over what is held, how sensitive it is, who can reach it, for what purpose, and how it is returned or destroyed.
IDG-ASR-003).IDG-TEC-011).IDG-TEC-006, IDG-PRC-013).Predictable, auditable controls for government, universities, health services, research institutes and enterprises receiving Indigenous data.
5 · How to Measure It
Governance claims are only as credible as their measurement. Following the ASD Essential Eight Maturity Model, each domain is scored at the level of its weakest applicable control, backed by cryptographically signed technical evidence and independent community review. Self-assessment is never presented as certification.
Control is absent or incomplete. One unmet applicable control holds the entire domain at ML0.
Documented policy, registers, agreements and baseline safeguards are active across scope.
Controls are technically or procedurally enforced, logged, and reviewed on an agreed cycle.
Automated checks verify every change and communities can directly inspect or verify records.
Runs every mapped unit test and verify script without leaking record content, signs the canonical JSON bundle with Ed25519, and anchors its SHA-256 digest in the tenant audit chain.
pnpm idg:evidence --tenant <slug> --key <pem>
Validates completeness, scores every domain by weakest applicable control, locks fixed non-certification attestation wording, and records the digest in the audit chain.
pnpm idg:assessment assessment.yaml --record --tenant <slug>
Communities review assessments independently (accepted, queried or rejected) with their own record reference, complemented by impartial partnership health checks.
IDG-ASR-001 · IDG-ASR-004 · IDG-ASR-005
| Domain | Focus | Proposed Controls | Automated Checks | Code Only | Organisational / Manual |
|---|---|---|---|---|---|
| GOV | Governance and authority | 5 | 2 | 1 | 2 |
| PPL | People | 12 | 9 | 0 | 3 |
| PRC | Process | 16 | 10 | 0 | 6 |
| TEC | Technology | 17 | 16 | 0 | 1 |
| ASR | Assurance | 5 | 3 | 0 | 2 |
| CON | Consuming entity | 13 | 0 | 0 | 13 |
6 · Verified Framework Crosswalks
Every external control identifier is verified against official publications (and
re-checked automatically against ASD and NIST OSCAL catalogues via
pnpm idg:verify-sources). No mapping is marked equivalent,
because every IDG control adds collective community obligations beyond organisational
security.
Global Indigenous Data Alliance (Sep 2019)
Primary people & purpose anchor (C, A, R, E) mapped on every control.
Wilkinson et al. 2016 / GO FAIR
Metadata, authorisation, provenance & community standards alongside CARE precedence.
Australian Indigenous Data Sovereignty Collective (2018)
Five Australian Indigenous data sovereignty principles mapped on every control.
Australian Signals Directorate (Sep 2026, OSCAL v2026.09.4)
58 verified data & security controls reconciled via automated OSCAL checks.
Australian Signals Directorate (Nov 2023)
Inspiration for strict weakest-link ML0–ML3 maturity scoring plus MFA, admin & backup links.
Attorney-General's Department
Australian Government protective security, personnel vetting, sharing & disposal links.
National Indigenous Australians Agency (May 2024)
APS Framework for Governance of Indigenous Data actions mapped as non-binding guidance.
OAIC
Individual privacy and breach obligations extended to collective community rights & harm.
NIST (OSCAL Verified)
62 verified security and privacy controls enabling enterprise assurance reuse.
Lin et al. 2020
Repository transparency, responsibility, user focus, sustainability and technology.
ISO / IEC (Paraphrased, Provisional)
Governing body evaluate-direct-monitor oversight placed explicitly below community authority.
Local Contexts Hub
Machine-readable cultural authority notices and protocols travelling with every record.
7 · Inspect, Test & Critique Openly
Every artefact below is generated deterministically from the validated YAML sources in
docs/idg/. Use the branded HTML manual for executive briefings and A4 PDF
printing, the CSV/Markdown catalogues for governance tooling, and the self-assessment
template to benchmark current practice.