AskBase memory
Shared registry · version 5
Sources, decisions and versions remain central. No consumer creates its own parallel truth.
Verified operational memory for the enterprise
Verified memory for your teams and AI agents.
The same facts, rules and permissions in AskBase and in your authorized agents.
Structured pilot
2 to 4 weeks
- 1 Support or Operations context
- 25 to 50 sources
- 3 to 5 users
- 30 to 50 real questions
Proof record · Support
Answer, passages and ownership
Business question
Which commercial gesture should apply after a delay?
Verifiedpermissions applied · audit active
Answer
Support can offer a 10% credit after verifying the delay. Any larger exception must be approved by the Support lead.
Document references
- Commercial policy · § 4.2
- Carrier delay procedure · page 3
- Validation
- Verified
- Validated by
- Camille Martin · Support lead
- Validation date
- August 5, 2026
- Access applied
- Support · before search
- Maintained by
- Support team
- Current edition
- Version 4
- Review
- Review scheduled for September 15
- Audit log
- Question · sources · validation · reuse
Trust registry
What makes an answer authoritative.
The answer is only one entry in the registry. The evidence supporting it remains readable.
- 01
Source and passage
Return to the precise document supporting the answer.
- 02
Verification status
Distinguish verified, sourced for review and known gaps.
- 03
Effective permissions
Apply access before search and response.
- 04
Owner
Know who maintains the rule or knowledge.
- 05
Active version
Keep history and restore without rewriting the past.
- 06
Maintenance
Prioritize expiry, obsolescence, gaps and contradictions.
- 07
Audit trail
Connect source, evidence, answer, validation and reuse.
Verified memory loop
Memory is verified at every step.
Each use produces a durable artifact. The answer remains connected to its sources, human decision and reusable version.
- 01 / 06
Authoritative sources
Connect the priority corpus and its permissions.
Stored artifact
Governed sources
- 02 / 06
Answer with evidence
Answer only with accessible passages.
Stored artifact
Evidence log
- 03 / 06
Expert validation
Confirm, correct or declare a gap.
Stored artifact
Attributed decision
- 04 / 06
Immutable knowledge
Create a version without changing history.
Stored artifact
Verified version
- 05 / 06
Governed reuse
Serve the same version to authorized people and agents.
Stored artifact
Usage by version
- 06 / 06
Continuous maintenance
Address freshness, gaps and contradictions exposed by use.
Stored artifact
Maintenance queue
Governance lineage
Every answer keeps its lineage.
The timeline connects access, source, version and human decision. A correction completes the registry without erasing what was used before.
- Source and requester
- The cited passage remains attached to the answer. A person’s permissions or an agent’s delegated identity are verified before search.
- Validator and rollback
- The registry attributes every decision. A correction creates a new version; a previous version stays visible and can become active again.
- Open gaps and contradictions
- Items without a reliable source, outdated items and contradictions remain visible until an owner resolves them.
Audit log
Answer AB-0427
Access verified before search
Support team · 2 authorized sources
Version used by the answer
Commercial policy · version 4
Validator decision
Confirmed by the Support lead
Correction without rewriting the past
Version 5 created · version 4 retained
People and agents
One verified memory, two governed access paths.
AskBase Chat and authorized agents read one shared registry. Every access stays bounded by an identity, permissions and a trace.
Bounded consumer
AskBase Chat
Teams query memory in their workspace.
- Sources
- Authorized passages
- Version
- Active verified version
- Permissions
- Effective access
- Trace
- Usage log
Person identity and team scope
Bounded consumer
Authorized agents via MCP
Agents query the same registry within an explicit framework.
- Sources
- Authorized passages
- Version
- Active verified version
- Permissions
- Effective access
- Trace
- Usage log
Delegated identity and quotas
First contexts
Start where knowledge needs to be authoritative.
Support and Operations concentrate recurring questions, exceptions and rules whose correct version directly changes the decision.
Context 01
→Customer support
Which commercial gesture should apply after a delay?
Answer with the validated procedure, authorized threshold and cited reply template.
Procedures · contracts · commercial policies
Context 02
→Operations and quality
Which procedure applies before a supplier audit?
Find the instructions, expected evidence and authoritative responsibilities.
Procedures · controls · quality standards
FAQ
Scoping questions, answered plainly.
Category, verification, permissions, agents and security: product limits are as explicit as its capabilities.
Guided pilot
A reliable context in 2 to 4 weeks.
AskBase frames an initial Support or Operations context, makes its sources legible and verifies what the team can reuse.
1 Support or Operations context
25 to 50 sources
3 to 5 users
30 to 50 real questions
Pilot price
€1,500 excl. tax
Deductible from an annual subscription signed after the pilot.
- 01
Select the context
Choose the operational scope and the owners responsible for it.
- 02
Connect priority sources
Gather 25 to 50 sources relevant to this context and its rules.
- 03
Test real questions
Have 3 to 5 users work through 30 to 50 real questions.
- 04
Validate the first knowledge
Confirm useful answers, their evidence and reuse permissions.
- 05
Decide what comes next
Deliver an evaluation grid and a documented continue-or-stop decision.