cloudinit-bot
f5133893c7
This commit records the v1.3 inboxos milestone ship in CI-LOG.md and updates .ciagent/config.json to reflect the v1.3 close: - .ciagent/inboxos/CI-LOG.md: new "v1.3 milestone" section with the ideation (946b744+d2f3bd5), plan (bc7280f), execute (8 commits), verify (94f4233), review (5bb9eed), audit (0801078), close (this commit), and ship record. The 9 lessons (L-IDEATE-V1.3-01..07 + L-PROC-V1.3-01..03) are recorded. - .ciagent/config.json: the inboxos project row updates from milestone: v1.2 / status: complete to milestone: v1.3 / status: complete. The v1.3.0 tag is on local (70b2dd1); the FF-merge to main is local; the Gitea release v1.3.0 is published (https://git.cloudinit.dev/jc-capital/inboxos/releases/tag/v1.3.0, published 2026-06-08 23:40). The remote push of main + the v1.3.0 tag + the milestone branch is admin-gated per the v1.0 / v1.1 / v1.2 close precedent (this repo's cloudinit-bot token does not have push-to-protected-main scope). The v1.3.0 release is published on Gitea. ---ci--- project: inboxos phase: 0 milestone: v1.3 status: ship_record ship_record: merge_commit:70b2dd1tag: v1.3.0 release_url: https://git.cloudinit.dev/jc-capital/inboxos/releases/tag/v1.3.0 release_published_at: 2026-06-08 23:40 tag_pushed: false main_pushed: false milestone_branch_pushed: false config_update: inboxos_milestone: v1.2 -> v1.3 inboxos_status: complete -> complete ---/ci---
InboxOS
Self-hosted personal ERP / CRM pipeline. A single Gmail inbox, polled over IMAP, archived to SeaweedFS, classified and extracted by a local LLM (Ollama), and written to NocoDB as structured records. Curated attachments are mirrored to Papra. No third-party SaaS touches PII.
Where to start
- Operations runbook —
docs/operations-runbook.md. System overview, service inventory, workflow operations, observability, failure modes, security, cost, glossary. The first thing to read on day 1 of incident response. - Extraction contract —
docs/extraction-contract.md. How a raw email becomes a NocoDB record. Source of truth for theinboxos:classify+inboxos:extract-<module>prompt family. - NocoDB schema —
docs/schemas.md. The four module tables (finance,crm,intel,promotions) and the Message-ID idempotency contract. - Gitea Actions setup —
docs/gitea-actions.md. Runner provisioning (including the second runner for live + historical parallelism), repo secrets, the Basic Auth model. - Pipelines —
pipelines/README.md. Flow diagrams, idempotency model, rollback procedure for the live and historical pipelines. - Papra write policy —
docs/papra-write-policy.md. When the pipeline writes to Papra (attachments + selected bodies), and why the first ship is dry-run.
Quick layout
inboxos/
├── README.md # this file
├── .env.example # placeholder env (no real secrets)
├── docker/
│ └── docker-compose.yml # self-hosted stack: gitea, runners, nocodb, seaweedfs, papra, ollama
├── .gitea/workflows/
│ ├── live-pipeline.yml # cron */5 * * * *, polls IMAP
│ ├── historical-pipeline.yml # workflow_dispatch, streams .mbox
│ └── ci-pr.yml # fast-tests + 100MB e2e + live Ollama smoke
├── pipelines/ # shared Python: common.py, live_pipeline.py, historical_pipeline.py, mbox_stream.py
├── .opencode/commands/ # version-controlled extraction prompts (prompt-as-code)
├── config/ # n8n config (legacy, no longer in use)
└── docs/ # this runbook + schemas + contracts + reports
Status
Phase 5 — Full Deployment. Parent goal: INB-1. Current phase issue: INB-7. The runbook in docs/operations-runbook.md is the canonical reference for ongoing operation.
Historical archive (Google Takeout .mbox)
The full Google Takeout .mbox export lives in SeaweedFS at the canonical S3 URI:
s3://inboxos/eml/historical/all-mail.mbox
That is the value to pass as the mbox_object_key workflow_dispatch input to historical-pipeline.yml. To verify it exists, run from any host with mc configured against the inboxos bucket:
mc ls --recursive inboxos/inboxos/ | grep '\.mbox$'
The historical pipeline streams this object message-by-message, UPSERTs each into NocoDB on Message-ID, and writes the raw .eml backup under s3://inboxos/eml/historical/<yyyy>/<mm>/<dd>/<Message-ID>.eml. See docs/operations-runbook.md §3.2 for the dispatch recipe and §4.4 for the full bucket layout.