KB-CRP-001 · v2.1 · CANONICALKey Takeaways
- Single Canonical Schema: Codifies the Frappe v16.50 data architecture for the Catalytic Resource Planner (
crp), uniting local-first SQLite development with auditable collective governance. - Instance-Centric LSA: Removes duplicate theoretical fields from operational tables by routing all Means of Liberation (MoL) and Means of Domination (MoD) tracking through the unified
Catalytic InstanceDocType. - Standard Field Protocol: Enforces six reserved fieldnames (
title,slug,capacity_points,status,color,description) across every module so Kanban boards, calendars, and search work polymorphically.
Connected Initiative: CMMNS.io & The Catalytic Resource Planner (/cmmns-crp)
How Our Software Schema Reflects Classless Relations
Architecture Is Never Neutral: Conventional enterprise resource planning (ERP) systems hardcode bosses, subordinates, and profit extraction directly into their database tables. When a community collective tries to organize inside unmodified corporate software, the software quietly pushes the group back toward hierarchy.
The Base Context Model (Who and Where): Rather than treating our base as a flat mailing list, every project and action in crp connects through a dynamic Base Context Link table to five foundational records: User, Collective, Geographic Area (Region -> City -> Neighborhood -> Block), Social Group, and Entity.
Unified Instance-Centric LSA: Operational records stay lightweight and fast because all Liberatory Social Accounting (LSA) classification lives inside the single Catalytic Instance DocType, tracking how each 3-week Narrative of Change erodes domination and consolidates liberation.
Frappe v16.50 lets developers and community stewards run the full
crp stack offline on Linux laptops using a single SQLite file before syncing to cloud production — turning database backups into sub-second file copies.The Standard Field Protocol Across All CRP DocTypes
Eliminating Schema Drift: Every DocType across our Principled Agility, Commons, Care, and Community Fund modules implements these six standard fieldnames so collective scripts and Kanban views work universally without custom overrides.
| Concept | Reserved Fieldname | Frappe v16.50 Field Type | Sociotechnical Purpose Across All DocTypes |
|---|---|---|---|
| Human Name | title | Data | Primary human-readable title used in title_field and search_fields across every module. |
| Unique URL ID | slug | Data | Readable, deterministic identifier for clean routing and cross-instance federation. |
| Holistic Effort | capacity_points | Int (Read-Only) | Numeric effort score populated from Effort Level (Small=1, Medium=3, Large=5) to respect Scope of Care. |
| Lifecycle State | status | Select / Link | Standard lifecycle state powering Frappe v16.50 Kanban swimlanes and UI status pills. |
| Visual Token | color | Color | Hex color code for calendar blocks, focus area badges, and LSA balance charts. |
| Main Explanatory Copy | description | Text Editor / Small Text | Plain-language body text explaining context, agreements, and acceptance criteria. |
Deep-Dive Module Specifications & Revision History
How This Piece Connects to Our Work
Tested this method in your neighborhood or have a critical refinement, field adaptation, or counter-perspective? Submit a dialectical response or partner proposal.