Source beta
Prepared 28 October 2026 for latintzar/ai-native-erp. This file records a source candidate; publication has its own commit/release record.
Included
The original Cedar workspace, shared kit/theme/scenarios, retained generated product paintings and build tools; the maintained FastAPI/PostgreSQL backend; selected prototype API adapters; Cedar’s native persistent collection service; source tests, typed models and deep ERP specifications. SOURCE.json pins upstream 12d77d610c82a21c602a7706861f043e16607a74. Per-file original blobs/hashes are retained in docs/release/source-baseline.json.
The export contains source rather than the private repository’s Git history, environment, runtime data or caches. The original mixed checkout remains unchanged and follows its own protected workflow.
Capability evidence
| Subject | Evidence in this preparation | Boundary |
|---|---|---|
| Cedar frontend | Fresh npm install; English and generated Spanish builds; app/scenario type checks; retained frontend tests | Synthetic browser state; maintained-backend adapter remains work |
| Shared kit | Fresh gallery build and retained semantic theme/components | Product adoption follows each actual workflow |
| Prototype APIs | 330 fixture tests passed, 3 existing skips | Provider transport/account acceptance remains separate |
| Native collection service | 249 tests and 49 subtests passed | Fixture bank/fiscal responses; seller/bank/SUNAT commissioning remains separate |
| Maintained backend | Fresh owned native PostgreSQL migration, Harbor account/catalogue/orders, order approval/value snapshot, HTTP authentication/CSRF, RLS and database restart persistence | Offline identity-provider fixture, captured effects; ingestion/model/provider proof remains separate |
| Source safety changes | Private provider-file tests and explicit founder/public-identity bootstrap regressions | Real account/operator configuration is installation-owned |
| Presentation | Six source-derived Cedar component captures with original fixture values and painting bytes | Authored component compositions, rather than live provider screenshots |
The recorded backend proof produces three products, two customers and two orders. The approved order retains its 1,650-cent value snapshot across PostgreSQL restart. Its ordinary HTTP operation records weight/audit and rejects foreign-tenant access. Runtime-role reads/writes demonstrate the scope wall.
Extraction decisions
- Cedar’s release build keeps English/Spanish source transforms and emits truthful export/upstream provenance. The original multi-project publisher and owner deployment jobs stay with their original environment.
- Actual private operator phones/email become reserved synthetic fixture identities. The fictional 68-SKU catalogue remains. Founder grants, sender addresses and outbound account identifiers require explicit installation configuration.
- Optional support uses an installation-owned VITE_SUPPORT_WIDGET_URL, with GitHub issues as its empty/default path. The original support account is not loaded. Copilot model evidence accepts the configured model identifier.
- Legacy browser identity bootstrap reads the installation’s explicitly public IdP identifiers and excludes privileged/secret keys. Provider keys stay in selected private files;
doctorprints names/status. - Existing initials Avatar replaces only the unlicensed Meta reference photograph. Product paintings, component design, typography, map/units/document systems and provider adapters retain their source.
- Compatible Vite/DOMPurify updates, removal of unused Android CLI tooling and a CJS-compatible
uuidoverride for ExcelJS clear the recorded npm audit findings. Excel/PDF and the retained frontend suite cover the affected export path.
Omitted and remaining
The separate Peru, Sofia and order-page applications retain their own source/release boundaries. Their private history, customer/company catalogues and operator deployment records are outside this ERP export. Named external legacy seed profiles remain private pending their own data provenance. Artisan, Bela and robotics source are outside this release.
The universal Cedar→maintained-backend adapter, designed intake/index/prediction/evaluation capabilities and other planned ERP integrations remain explicit engineering work. The local SKU artwork request store and the separate Ideogram service retain their real boundary. Own-key configuration presence is distinct from a successful provider receipt.
All preparation used zero model/provider/GPU calls. Actual IdP, model, telephony, email, bank, payment and fiscal acceptance requires the selected installation’s accounts and measured commissioning. The public-preview funding gateway is separate and does not replace the original provider architecture.
See verification, decisions, architecture and third-party notices.
Initial publication changes record the small release-time fixture and text normalization changes.