Archived
Add protected historical household document ingestion and retrieval #31
No Assignees
No due date set.
Dependencies
No dependencies set.
Reference: KofTwentyTwo/carl#31
Reference in new issue
Block a user
Carl needs a protected way to import household documentation and historical assertions without replacing current financial records or treating dated summaries as verified statements.
Implement consumer-owned historical source records with observation/effective dates, immutable content identity, provenance and explicit verification status; permission-controlled original content; idempotent ingestion and reconciliation; native upload/review actions; and bounded caller-aware conversation reads/citations. Retrieved document instructions must remain untrusted data. Source/account/artifact permissions and revoked-access checks must apply before retrieval and export.
Existing tax-document evidence text and current home/debt/expense records cannot safely stand in for generic historical custody. Do not silently load an old schedule as a current expense or an installment due date as a payment receipt. Accept current financial fields only through explicit evidence review.
Acceptance: actual PostgreSQL and negative permission/revocation tests, repeated import/content identity, truthful dated/unverified responses and a real privately held document through UI-to-service-to-chat retrieval. Private documents, paths and derived financial values must remain outside this public repository and CI artifacts.
Related: #28 and #30. Whole-system knowledge/financial priming remains incomplete until supplied evidence and this capability are qualified.
October 2: protected original custody is implemented locally and accepted for ten actual privately held historical notes through native upload, immutable preview/confirmation and original download. Stored originals are byte-identical, PRIVATE/SUPPLIED_UNVERIFIED with supplied dates, no-store and anonymously denied. V61/V62 actual retained migration/reader/source preservation checks pass in the installed563/FlywayV62 package. Documents are linked to the source-grounded readiness DRAFT/report without manufacturing current terms or payment states.
Specific actual Anthropic document reads and source citations have independent current-access/audit/usage checks; their exact package provenance is retained. Those backend cases do not qualify the owner’s ordinary native chat, currently failing in #28/#34. Complex document-to-plan retrieval has a bounded-summary repair with50 focused controlled SDK/PG tests; full matching package and actual owner chat acceptance remain outstanding. Keep private originals/values/paths and raw model text outside GitHub/source/CI. Do not close whole-system knowledge or financial priming from these ten historical notes.