Overview
Macro treats workplace integration as a context problem: work should retain its origin, access rules, current state, retrievable evidence, and next action as it moves between specialized blocks. The series follows those relationships from mentions and permission edges through conversation-to-task-to-GitHub workflows, Inbox, Search, and Memory, then examines CRDT collaboration and agents acting as permission-bound peers. Its conclusion is conditional: connected context can reduce handoff loss, but freshness, indexing, sharing, imports, agent edits, hosted-service claims, and review remain governance and operational responsibilities.
Learning outcomes
- Macro’s central value is preserving relationships among specialized work surfaces, not merely placing integrations behind one login.
- A durable work path keeps origin, access, current state, retrieval, and action connected, while each surface retains its own semantics and policy.
- Inbox, Search, and Memory are different projections: attention, literal evidence retrieval, and synthesized background.
- Agents can act as attributed peers through shared state and workflow-shaped tools, but permissions, freshness, review, and recovery remain responsibilities.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
What makes Macro different from a collection of integrations?
Macro treats integration as durable relationships among specialized blocks, not just data or links copied between applications. Its value depends on preserving origin, access, current state, retrieval, and action across handoffs.
How does Macro keep work connected from conversation to completion?
Macro can link a message or email to a task and associate that task with a GitHub pull request. Under documented conditions, branch, review, and merge events move the task through In Progress, In Review, and Done; those states do not by themselves prove deployment.
What is the difference between Macro Inbox, Search, and Memory?
Inbox handles attention, Search retrieves indexed literal evidence, and Memory provides synthesized background for agents. Notifications are not work state, Search is not semantic or necessarily immediate, and Memory is not a live transcript.
When is Macro’s context-native design a good fit?
Macro is a stronger fit when costly failures occur at handoffs among conversations, tasks, code, customer context, and agents. It is a weaker fit when uniform access, immediate semantic retrieval, full-fidelity external sync, or independently verified guarantees matter more.