Docs / Compliance

Hackathon Compliance Report

Requirements mapping, technology stack, workflow coverage, and data management evidence. This page is the designed platform reading surface for the compliance evidence.

Identity and trust

World ID, eID/OIDC, Didit KYC, passkeys, biometric return login, DPI inspection, and public privacy controls.

Enterprise intelligence

Official-source company search/registration, Companies House/SEC/OpenCorporates grounding, immutable source rows, scoring, audits, and financial analysis.

Government and civic workflows

Geo governance, councils, claims, campaigns, residency-gated voting, GovLedger, public institutions, and HumanityOS readiness.

Labor and education

Jobs, applications, contracts, document sharing, portable career levels, diplomas, certificates, self-taught projects, inventions, and patents as profile evidence.

Data management

Append-only official sources, score facts, audit trails, proof references, document intelligence, and no-source/no-score policy.

AI workflow coverage

Gemini agent orchestration, real tool chain visibility, conversation history, file/image/document analysis, camera/voice controls, and grounded source disclaimers.

Technology Stack

Next.js 16 App RouterPostgreSQLPM2TailwindGemini 2.5 FlashCompanies HouseSEC EDGAROpenCorporatesPrismAPIDiditWebAuthn/passkeysDPI Lobster Trap

Evidence

  • Official company facts come from external registries and are stored as immutable source rows.
  • Profile evidence and scoring upgrades are now visible through citizen and enterprise proof pages.
  • Claims and votes require verified identity, World ID uniqueness, and residency proof for region-scoped actions.
  • AI responses expose tool steps, sources, DPI decisions, and no-provider/no-data disclaimers.

Open Hardening Items

  • Real eIDAS/OIDC provider registrations and mandate registries remain production integrations.
  • Residency and profile proof references need encrypted file storage, expiry, revocation, and reviewer queues.
  • Native fingerprint hardware depends on browser and operating-system WebAuthn support.
  • Full statutory geo coverage needs national council registries and boundary reconciliation beyond GeoNames.