Local execution / content-addressed runtime
reinforcing
The actor's executable face is pinned by CID; reach comes from content-addressed code, not a hidden server.
actor-specific system dynamics
Kyber — open-kyber ERP (kotoba WASM actor)
Kyber — open-kyber ERP as a content-addressed kotoba WASM actor. The ERP business logic (accounting GL / AP-AR / inventory / the kotoba-native productivity suite) compiled to a `kotoba-node` WASM component that the kotoba host / e7m-wasm-runner stores on IPFS (by CID) and runs, writing canonical ERP state straight into the kotoba Datom log via the `kqe` host import — no Cloudflare Worker, no XRPC→PDS hop. Multi-command dispatch over `run(ctx_cbor)`. R3 PoC (kyber-erp-core: createAccount / seedChartOfAccounts / createJournalEntry double-entry-validated + best-effort trial-balance/coverage reads); full 28-command port per WORKER-AS-WASM-ACTOR-MIGRATION.md. Per ADR-2606037200.
Role lens: Local execution / content-addressed runtime.
Identity
kyber
Ktier-bcompiledsystemappview
Runtime
WASM + 2 service endpoints
source compiled · status r0 · vm 0 verification methods
AtprotoPersonalDataServerAtprotoXrpc
Surface
00-contracts/schemas/erp-ontology.kotoba.edn
performer system · ui appview · adr 2606037200
Energy flow
Flow score6.5/10
prior 1.6 · evidence 2.1 · policy 3.3 · surprise 0.4
Boundary / no-server-key
balancing
The actor stays inside the charter boundary: no server-held key, no hidden impersonation, and no unbounded authority. Source = compiled, status = r0.
Repair / drift control
balancing
ADR coverage 2606037200, services WASM + 2 service endpoints, vm 0 verification methods, primary surface 00-contracts/schemas/erp-ontology.kotoba.edn.
Boundary Conditions
- did:web:etzhayyim.com:actor:kyber
- profile handle kyber.etzhayyim.com
- source: compiled
- services: WASM + 2 service endpoints
- no server-held key
- no external assets
- no cookies