Context & memory
Foundry holds what your organisation knows: the entities, decisions, precedents and history that make every answer and every mission specific to you.
Organisational memory
written by governed work, held with its permissions
ENTITY
Supplier ACME Steel: approved, 60-day terms, 14 contracts on record
PRECEDENT
Cross-border tenders route to legal for arbitration-clause review
RULE
Discounts above 8% need commercial director approval
MISSION
RFQ-118 resolved: comparison approved, terms set at 75 days
Why it matters
A model knows the world. It doesn't know your suppliers, your thresholds, or what your team decided last quarter. Context & memory is the difference between generic intelligence and your organisation's intelligence.
What Foundry holds
Permissioned, masked and audited like everything else
ENTITIES
Who and what
Suppliers, clients, projects, contracts and people, linked across your systems.
DECISIONS
What was decided
Approvals, exceptions and precedents, with who decided and why.
RULES
How you operate
Policies, thresholds, preferences and the exceptions your teams live by.
HISTORY
What has been done
Every past mission and its outcome, available as context for the next one.
Memory compounds.
Every mission leaves the organisation smarter. The second workflow is faster and cheaper than the first because Foundry already knows the terrain.
FIRST MISSION
Learns the terrain
Connects the sources, maps the entities, meets the rules and the people who own them.
MEMORY WRITTEN
The work becomes context
Entities, decisions and precedents from the mission are written back, with their permissions.
NEXT MISSION
Starts ahead
Opens with the suppliers known, the thresholds loaded and last quarter's decisions in reach.
Memory is one part of the layer.
Foundry pairs it with model routing, grounded retrieval and governance.
Explore Edrak Foundry →Explore Edrak Foundry →