2ndBrain · Proprietary system
2ndBrain: the company's memory, with agents that prepare the work and people who decide.
It is the system we implement on. It brings together what is scattered across emails, folders and people, answers with the source, and lets agents work on that same memory. We designed and built it at Avonlea, and we use it in our own operation.
Any given Monday
The answer exists. It is scattered.
Without a shared memory
- An email from March
- Two spreadsheets
- Someone out in the field
Takes the morning
Monday, 9:00. Management asks which guarantees expire this quarter and how much margin is left on the contract. The answer exists: it sits in an email from March, in two spreadsheets and in the memory of someone who is out in the field today. Putting it together takes the morning. Next Monday, it gets put together again.
With a second brain
- An email from March
- Two spreadsheets
- Someone out in the field
2ndBrain
Seconds, with the source in view
Monday, 9:00. The same question is answered in seconds, with the source document in view. An agent has already left a draft of the weekly report; a person reviews and approves it. What was learned on this contract is available for the next one.
How it works
Every answer starts from a document and every action ends in an approval.
-
Load
Contracts, drawings, minutes, spreadsheets and manuals come in classified: scope, who can see it, layer and status.
-
Ask
An authorized person asks in plain language and gets the answer with the source document.
Illustrative questions
- Which guarantees expire this quarter, and on which contract?
- What did we agree with the supplier at the last meeting?
- What does the equipment manual say about this alarm?
- What is pending for each area this week?
-
Propose
An agent drafts the report, the minutes, the alert or the reply. It stays a draft.
-
Approve
A person reviews and approves it. Every change is logged with actor, action and date.
What it includes
Six components hold up the memory and its controls.
Memory in three layers
Information What the documents say.
Control What it costs, what risk it carries and when it expires.
Actions What needs to be done and how.
Access by level and area
Every document has a level (internal, restricted or confidential) and an area. Each person and each agent sees what corresponds to them.
- Internal
- Restricted
- Confidential
Data kept apart from analysis
Seven statuses, from original source to agreement. What a document says is kept apart from analysis, hypothesis and proposal.
Agents with approval
Versioned agents with bounded tasks. What they produce enters a drafts inbox and leaves with approval.
Project management that stays current
Items, dependencies, open items with an owner and a Gantt chart, updated by the same agents doing the work. The record stays alive when the one doing the work keeps it.
Auditable
Every change writes an event with actor, action and content, inside the client's instance.
Integration
It does not replace the ERP or the document repository: it uses them as sources.
- ERP
- Document repository
- Emails and spreadsheets
The client's 2ndBrain instance
MCP
AI assistants the team already uses