The organizational context layer for people and AI
One structured model of how the organization works. Readable as documentation, a process map, and context for agents—without replacing the tools you already run.
Junctive is in development. This page describes the intended product.
Meridian Group · Vendor Payment
Document
Vendor Payment
Pay approved vendor invoices accurately and on terms.
Trigger
Approved invoice received
Outcome
Payment issued and accounting entry reconciled
Owner
Finance Manager
Systems
Sage, Bill.com
Policies
Purchasing Policy, Delegation of Authority
Vendor Payment runs continuously, with a weekly payment batch on Thursdays. Exceptions above the approval threshold route to the Finance Manager.
The model
Processes, roles, systems, and policies—connected on purpose.
Processes
Capture what starts the work, the steps and decisions, and the expected outcome.
Roles
Record who takes part and who is responsible, so your team knows where to take questions.
Systems
Connect each process to the tools it uses. Your team keeps working in its existing systems.
Policies
Connect policies to the work they govern, so people can see which controls apply to a process.
One model, multiple views
Document and map stay synchronized.
Vendor Payment
Document
Vendor Payment
Pay approved vendor invoices accurately and on terms.
Trigger
Approved invoice received
Outcome
Payment issued and accounting entry reconciled
Owner
Finance Manager
Systems
Sage, Bill.com
Policies
Purchasing Policy, Delegation of Authority
Vendor Payment runs continuously, with a weekly payment batch on Thursdays. Exceptions above the approval threshold route to the Finance Manager.
Vendor Payment
Map
Vendor Payment · Map
StartInvoice received
ActionValidate invoice and POAccounts Payable · Sage
Update the process once. Its document and map stay in sync. Both views use the same recorded steps, owners, systems, and decisions, while the document also has room for written guidance.
Start with one process your team knows. Describe the work, review the proposed steps and connections, and assign an owner. Your team keeps that information current as the way you work changes.
Ask the Organization
Find owners and understand dependencies.
“Which processes use Salesforce?” “Who owns Vendor Payment?” “What is affected if Sage is unavailable?” The intended question tool looks up recorded relationships and explains the results. Answers depend on the coverage and accuracy of your map; missing or outdated information limits what it can tell you.
Ask the Organization
Question
What processes are affected if Sage is unavailable?
Vendor PaymentOwner · Finance Manager
Vendor OnboardingOwner · Finance Manager
PurchasingOwner · Operations Manager
Month-end closeOwner · Finance Manager
Expense reimbursementOwner · Finance Manager
Shipping dispatchOwner · Operations Manager
6 of 24 example processes use Sage · scripted preview
Agents
Give agents the context your team has reviewed.
The planned read-only connection for AI agents uses Model Context Protocol (MCP). It gives agents access to recorded processes, roles, systems, policies, and dependencies when they need business context.
AI can help draft a process from a plain-English description. A person reviews the proposal before it is saved. Shared context supports better informed answers; human review remains part of the workflow.
Portability
You keep the files.
The intended product includes workspace export as Markdown and structured records, so your team can keep and reuse the information it has captured.