Foundry OS is ADEPR's fundamentals layer.
Foundry does not ask pastors, finance coordinators, or regional teams to learn a new way of working. It meets them inside documents, spreadsheets, PDFs, and tasks, then adds the structure ADEPR needs around that work.
Do not reinvent the work. Organize the work.
Familiar documents
Pastors work in DOCX reports, finance coordinators work in XLSX budgets, and regional offices review PDFs without learning a foreign editing surface.
Structured submission
The work still feels like a document. What changes is where it lives, how it is submitted, and how the organization tracks it afterward.
Offline resilience
Foundry is a Tauri desktop application, built for Rwanda's connectivity realities, with local editing and sync when connection returns.
Open task. Do the work. Submit.
For most users, this is the whole experience. Foundry handles routing, storage, notifications, version history, and Thread attachment in the background.
Open task
A pastor sees the church Space and the tasks assigned across pastoral administration, finance, youth ministry, and other configured sub-Spaces.
Do the work
The attached DOCX, XLSX, or PDF opens directly in Foundry. The user edits the document using the format they already understand.
Submit once
The Submit button saves, versions, routes the file back to its Thread, updates the task, and notifies the right people.
A self-hosted document engine, wrapped in ADEPR structure.
Foundry borrows from mature open source document tools and adds the operating layer around them. ADEPR keeps native files editable across their whole lifecycle.
Built as a real desktop application.
Foundry OS uses Tauri: a Rust backend for security and performance with a Next.js frontend for the interface. Local users can keep working when connectivity drops.
Offline editing
Tasks and documents can be opened and edited locally for single-user work.
Versioned submissions
Every submit creates a new version. The Thread keeps who, when, and what changed.
Conflict visibility
Simple cases sync cleanly. Conflicts are surfaced instead of silently overwriting work.
Fundamentals first. Collaboration after.
Core desktop shell, Spaces, task list, DOCX/XLSX open-edit-submit, offline sync
PDF annotation, PPTX support, visible version history, submission notifications
Thread-generated tasks, task routing, Thread version history
Profiles, Capability Index, cross-Space Threads, collaboration fabric