abstraksi/ — the spec and strategy hub

The working hub for the Aksara vision: Aksara (device + runtime + aksara-cli), ETNOS (federated forum), CARE-as-Code, and PT Abstraksi Data & Kognitek. The canonical narrative source is ~/workspace/Aksara_Master_Proposal_v4_1.docx; this folder is where it becomes specs, decisions, research, and the Papua Tengah proposal.

How this folder works

00_FRAMING.md is the why. Specs are the what. DECISIONS.md records every settled or open call as D-numbers; specs cite D-numbers instead of re-arguing. LEDGER.md is the single list of things that need Yose's hands. GLOSSARY.md owns names.
research/ files are dated and sourced; a research claim without a URL and access date does not get cited by a spec.
Every spec starts as STUB, becomes DRAFT, then FINAL. Status line at the top of each file.
House style everywhere (D13): no em dashes, honest labels on unbuilt things, Indonesian-first user surfaces, every number carries its source.

Map

Path	What	Status
`00_FRAMING.md`	The 2026-07-05 framing: crown jewels, settled positions, moat stack, ontology test, build order	LIVE
`DECISIONS.md`	D01-D19 decision records (D17 Memori Aksara, D19 display)	LIVE
`LEDGER.md`	Needs-from-Yose	LIVE
`GLOSSARY.md`	Canonical naming, one name per thing	FROZEN (D10 settled)
`research/`	7 dated scout reports: context distillation, APBD/Otsus window, stack+hardware SOTA, procurement feasibility, memory stack, display options, Alibaba CoCreate	7 landed 2026-07-05
`specs/communal-ai/`	Category, entity schema, Civic Transaction protocol	STUBS
`specs/aksara-cli/`	Principles, core surface, gates+conformance, signed-record standard, skill packs, agent contract	STUBS
`specs/care/`	Policy engine, consent+revocation, legal review path	STUBS
`specs/etnos/`	10 specs DRAFT: 00-06 core (seam, fork delta, federation ext, civic namespace, agents-in-forum, release gates, transparansi+index), 08 musrenbang, 09 social-core, 10 design-language; plus 07_horizon brainstorm (21 futures, 3 tiers, anti-features)	10 DRAFT + HORIZON
`specs/device/`	05 design-language DRAFT (Perapian bukan wajah), 06 UI-sim PLAN, `blueprints/` v0.4 "Plakat" HTML engineering blueprint (regenerable); device spec, BOM, provisioning+keys, Indera line, resilience mesh still STUB	05 DRAFT · BLUEPRINT v0.4 · rest STUB
`specs/memori-aksara/`	00 seed + 01 arsitektur (BRAINSTORM, enam laci + lane B) + 02 format `.aksara` v0.1 (DRAFT); reference-impl repo: github.com/yohn-maistre/memori-aksara	02 DRAFT · D20 naming open
`specs/security/`	Unified threat model, UU PDP compliance	STUBS
`ops/`	03 legalitas LIVE (runbook); zero-cost deploy, demo protocol, evals STUB	03 LIVE · rest STUB
`company/`	Operating doc, funding tracker (supersedes v4.1 §49)	STUBS
`proposal/`	`README.md` package manifest + Yose-fill checklist; exec summary (DRAF v0.2, 2-hal), concept note (v0.2, 4-hal), profil perusahaan (v0.1), surat audiensi ×2, GAMBAR pack (11 SVG, DONE), v4.1 errata (12 rows)	NABIRE PACKAGE DRAFTED

Pre-existing context docs (root of this folder)

YOSE_AKSARA_MASTER_MEMORY.md, aksara-cli domain Research Report.md, CLIs Research Report.md, forum-readiness-alpha-beta.md, README-atproto-agent-network.md. Distilled in research/2026-07-05_context-distillation.md. Proposal: move them under research/legacy/ once Yose confirms nothing else links to these paths.

Related material outside this folder

~/.hermes/workspace/papers/ P01-P03 and ~/.hermes/workspace/blogs/ 01-11: Yose's thinking scaffolds; specs lift content, never prose (scaffold prose violates house style).
~/workspace/code/honai-metro: the Honai Metro fork (ETNOS client).
~/workspace/code/aksara-papan: the panel UI (browser-first e-ink sim), github.com/yohn-maistre/aksara-papan (private until Yose flips it).

Current priorities (from research, 2026-07-05)

KUA-PPAS 2027 window is open for weeks: concept note to Bapperida + Diskominfo Papua Tengah is the most time-critical artifact (proposal/00).
BRIN RIIM Batch 2 closes 31 July 2026; needs a campus partner (company/01, LEDGER).
Build order for demos per 00_FRAMING §6, adjusted for the Oracle free-tier cut and the WhatsApp policy risk (ops/00, ops/01).