Information Layer
Target source-backed relationship context.
Information Layer
The information layer is not implemented yet. It is the target layer that should turn raw communication and system activity into usable operating context.
Target information#
| Information type | Examples | Target behavior |
|---|---|---|
| Messages | email, chat, portal comments, form submissions | resolve to relationship timelines and workstreams |
| Files | PDFs, spreadsheets, security docs, implementation files | classify, summarize, permission, and link to records |
| Contracts | MSAs, SOWs, order forms, amendments, DPAs | extract obligations, terms, renewal dates, parties, and risks |
| Decisions | approved scope, timeline changes, pricing exceptions | preserve source and approver |
| Requirements | technical, security, operational, procurement, legal | track owner, status, and source |
| Risks | blockers, overdue tasks, missing docs, vendor issues | route to owners and escalate when stale |
| System fields | CRM stage, ERP vendor status, invoice state | sync with confidence and approval rules |
Target condensed records#
Arn should eventually maintain current-state records derived from source events:
- account brief
- vendor brief
- implementation status
- contract summary
- open asks
- active risks
- decision log
- obligation list
- file inventory
- renewal and amendment context
Each record should show what changed, why it changed, and which source event supports it.
Target source confidence#
Not every source should have the same authority. Signed contracts, customer messages, internal chat, portals, CRM fields, and generated summaries should carry different confidence and authority.
AI-generated summaries should never be authoritative by themselves; they should point back to source events.
Current status#
There is no relationship information layer, file index, contract store, extraction pipeline, source confidence model, permission-aware search, or retrieval system in the current repository.