Project status and next work
This status describes the source reviewed for the documentation modernization. It is not a live service dashboard.
Current foundation
Section titled “Current foundation”Local inference, embedded RAG, API access, model routing, repository prompt/playbook assets, and static documentation are implemented. Their presence does not remove the limitations below.
Known implementation work
Section titled “Known implementation work”| Area | Work required before stronger claims |
|---|---|
| Security | Address tracked credentials, credential logging, ownership checks, and shared semantic history |
| Memory | Retrieve recent messages and remove expired content from both stores |
| Deployment | Repair Docker/service import paths and deploy exact revisions |
| Recovery | Capture complete consistent state and verify restoration |
| Configuration | Wire documented settings into consumers or remove unsupported settings |
| Validation | Make routing mismatches fail tests; add meaningful API and isolation checks |
| Performance | Avoid blocking the API worker during long inference |
These are backend/operations changes, not fixes implemented by this documentation update.
Experimental work
Section titled “Experimental work”The model-training pipeline and planner/executor workflow need broader evaluation. Training artifacts establish that an experiment produced files, not that a new model is ready to replace a baseline.
Future extensions
Section titled “Future extensions”Kubernetes/cloud deployment, SSO, multi-tenant support, advanced security controls, certification, and automated learning progress are potential future work. They are not current installation choices or available labs.
Next: Pick a scoped issue and follow the contribution workflow.