Capture & Intake
Turn incoming material into traceable candidates for action, knowledge or review.
Primitive uses capture/intake as the front door for unstructured material and Control inboxes as an operational message substrate. The target is one lifecycle from arrival to classification, promotion, work or archive.
When something new arrives, Primitive should not just throw it into a giant inbox. It should remember where it came from and help decide whether it is a task, an idea, evidence, a duplicate, something to research or something to ignore.
Capture is intentionally weaker than canonical knowledge. Intake preserves the original input and provenance first, then allows classification, deduplication, contradiction detection and promotion. Operational Control inboxes use the same principle for machine-to-machine work signals.
Candidate state
Captured material should enter a candidate state before being promoted into durable knowledge, decisions or work objects. This protects the system from treating every inbound claim as established truth.
Operational inboxes
Control inboxes act as the message substrate for orchestration signals. Workspace Inbox is designed as a view over that substrate rather than a competing control channel.
Lifecycle
The intended lifecycle spans intake, classification/sorting, candidate evaluation, promotion or routing, and retained provenance.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.