Carl AI
Carl helps the family get out of debt, improve rental/tax planning, and prepare to invest. It is a standalone family agent application: its domain model, PostgreSQL records, deterministic capabilities, reasoning, QQQ administration, and workflows form one product. Carl must understand permitted debts, assets, cash flow, budgets and rental properties, compare financial plans, and assist with tax preparation and ownership-structure analysis. Version 1 also reads bills, Synology CalDAV calendars/reminders and vendor records, produces reports, and prepares local drafts. It may maintain the authorized shared Synology plan calendar/reminders. It cannot send vendor messages, book external services, pay, purchase, trade, or make commitments.
Implementation is in progress. PostgreSQL, native QQQ HTTP/browser, permission and deterministic calculation checks pass for implemented slices; the full requirements are not complete. Live integration and production qualification are not claimed. Start with requirements, financial planning requirements, confirmed decisions, implementation work, and acceptance evidence. Development uses synthetic data only. This development branch selects foundation0.5.0-SNAPSHOT with exact Next UI1.0.0-RC.8 and the approved QQQ4.1 development snapshots; no QQQ4.1RC is published. The final408-test clean build,113 browser checks across seven synthetic suites,10 public generator tests, actual public PostgreSQL import/reconciliation gate and269-package artifact/image scans pass. Final evidence binds the package and qualification limits. The native sidebar lists apps/tables, System contains Operations/ESB/database diagnostics, and Chat with Carl stays available in a lower-left dock. Public fictional fixtures include full transactions/balances, homes/mortgages/rentals and protected shared/private records. Live inference, household integrations and hosted release remain unqualified; the immutable release baseline remains foundation0.4.1.
Build and local verification
Use Java 21, Maven 3.9+ and Docker for disposable PostgreSQL tests. Run mvn spotless:apply verify; the distribution is target/agent. Open this directory as a Maven project in IntelliJ, select Java 21 for the project and Maven runner, and run the same verify lifecycle. AgentApplication.main and tests use the same component factory.
The current parent is com.kof22:kof22-agent-parent:0.5.0-SNAPSHOT, now independently published and qualified from foundation main1464b10/run36878751071. Carl’s current frozen package was built with separately qualified local development artifacts; use -Dmaven.repo.local for that exact cache. Fresh Carl remote resolution still requires authorized private package credentials. The remote release baseline in config/release/foundation.json deliberately remains0.4.1: RC/stable promotion will refuse this development parent until its matching foundation release is published and independently qualified. A clean public-consumer checkout still needs private Maven package access for published artifacts. The final consumer build is verified separately from upstream publication. The consumer repository token alone is not assumed to grant cross-repository package access. Supply secrets privately through the environment and use --settings config/maven/settings.xml.example; do not store a token in this repository.
Run packaged browser checks with npm ci --prefix scripts/e2e, npx --prefix scripts/e2e playwright install chromium, then bash scripts/verify-browser.sh after the Maven build. The fixture uses synthetic PostgreSQL records and local TLS/OIDC; ordinary checks use a disconnected model. Set CARL_QUALIFIED_DISTRIBUTION to the reviewed distribution and run scripts/verify-dashboard-browser.sh and scripts/verify-talk-browser.sh for the native process UI checks; run scripts/verify-docked-chat-browser.sh for the dock; scripts/verify-qbits-browser.sh checks actual OpenSearch and Artemis integration. Live synthetic preview inference is separately opt-in and requires the already-authorized credential through ANTHROPIC_API_KEY; never paste it into source or configuration. Optional MAVEN_SETTINGS and MAVEN_REPO select an isolated qualified development cache.
Run the representative model evaluation against the frozen reviewed package. Controlled tooling is qualified; real model cases require an explicitly selected model and privately supplied authorized credential.
See operator instructions, family API integration, and acceptance evidence. Do not connect personal sources or expose this development application publicly until the outstanding acceptance and deployment work is qualified.
The build journal drafts document Carl’s creation using synthetic examples and explicit qualification boundaries.