Workpads Standard v0.1

The Standard

Eight numbered sections form the normative core. Each is versioned independently. When implementation and standard conflict, the standard governs.

Normative Sections

01
PADS Data Model
The structure of a workpad record — the atomic unit of the format. Defines field names, types, cardinality, and the three-record vocabulary (open, active, complete).
pads-model.md · v1 · 2026-04-27
02
Record Schema (svc-basic)
Canonical field definitions for the baseline service record type. The minimum viable record: worker, client, service, status, and optional financial fields.
record-schema.md · v1 · 2026-04-27
03
Naming Convention
How records, fields, record types, and implementations are named. Establishes the slug vocabulary and the URL scheme prefix convention.
naming-convention.md · v1 · 2026-04-26
04
RecordService Interface
The programmatic surface for creating, reading, updating, and persisting workpad records. Defines the contract that implementations must satisfy.
record-service.md · v1 · 2026-04-27
05
Codec & Compact Encoding
The binary encoding that produces a URL-safe hash fragment small enough to travel over SMS. This is the interoperability core: any conformant encoder and decoder must be compatible.
codec.md · v1.1 · 2026-04-28
06
Storage Adapter Contract
The interface between record logic and platform-specific storage. Allows the same business logic to run over IndexedDB, file storage, or in-memory backends.
storage-adapter.md · v1 · 2026-04-27
07
Two-Build Strategy
How a single codebase produces both a KaiOS 3.x build (D-pad, feature phone) and a modern web build. Defines the build targets and the split points in the code.
build-strategy.md · v1 · 2026-04-27
08
BASICS Conformance Mapping
The explicit mapping from Workpads Standard v0.1 to the BASICS Core tier. Enables formal interoperability claims and deviation registration.
basics-conformance.md · v1 · 2026-04-27

Extended Specifications

These documents are part of the standard and cover features in active implementation or scheduled for v0.2.

Document Scope
record-philosophy.md The five properties of a workpad record — foundational rationale for all design decisions
activity-profile.md Activity Profile and Block Registry — sender identity, contact store, location store
chain-protocol.md Record chain protocol — linked records, ACK mechanism, multi-worker pre-seeding (v0.2)
participants-block.md Participants block — typed party list replacing simple worker text field (v0.2)
financial-block.md Financial block — amounts, currency, tax, qty×rate, compound invoicing (v0.2)
transaction-classification.md I>O notation for income/expense direction, time, and settlement state
personal-platform.md Two-engine architecture: Exchange Engine + Learning Engine
panel-access-model.md Panel navigation model (ArrowLeft/ArrowRight) for platform input adaptation

Maintenance Documents

Document Purpose
ECOSYSTEM.md Map of all repos, tools, and how they connect
implementation-notes.md Pre-publication scan: deviations and innovations found in v0.1 implementations
codec-sync.md Protocol for keeping codec implementations in sync across products

Versioning

Section versions use v1, v2, etc. A section version increments on breaking changes only (field removed, encoding slot reassigned). Additive changes do not increment existing section versions.

v0.2 Roadmap

The following are settled in design and documented in extended specs, pending implementation:

  • Financial block in codec (§financial-block.md)
  • Chain protocol (§chain-protocol.md)
  • Participants block (§participants-block.md)
  • KaiOS 2.5 build target (§build-strategy.md)
  • URL scheme tag alignment across all implementations
  • Block Registry v0.2 schema with typed customers and locations