02 · THE CHALLENGE
Less searching.
More continuity
Client work, sourcing decisions and daily operations depend on context. When that context stays in inboxes and individual memory, every handover starts again.
Re-reading
Scroll through old messages to recover a client’s history, preferences and the right tone.
Uncertainty
Find a working rule without knowing whether it is verified or when it was last checked.
Repeated handovers
Explain the same background each time a person or an AI assistant joins the work.
03 · CORE CONCEPT
Give context
a consistent home.
One living record per client. One reference page per topic. One file per partner.
WIKI brings these records together through shared templates, clear status conventions and a routing layer. People and file-enabled AI assistants follow the same written method to find, maintain and use the knowledge.
The vault holds the operating knowledge around your work. Master transactional data, such as CRM records, stays in its existing system.
Operations Registry
Client and prospect records, communication profiles, service history and next-action ownership.
Knowledge Base
Country and topic references, verification states, shared concepts and partner records.
04 · KEY FEATURES
Eight capabilities.
Four connected views.
Explore the records, reference structure, operating method and export that make WIKI useful. These source-pack visuals are diagrams and demo illustrations, rather than live interface screenshots.
CLIENT CONTEXT
Know the client. Keep the thread.
Keep language, tone and contact preferences beside a one-line status, next-action owner and dated history. Start the next reply from a living record.
-
Client communication profiles
-
Status and next action
REFERENCE KNOWLEDGE
Make the state of knowledge visible.
Reusable page templates and structured headers keep country and topic references consistent. Draft, verified and source-pending states, plus review dates, show what still needs attention.
-
Consistent page templates
-
Visible verification status
THE OPERATING METHOD
Find. Update. Record the change.
The routing layer directs a person or assistant to the right record and voice guide. Written instructions guide updates; Git preserves the change history. The illustrated ingestion workflow is operator-guided.
-
A route to the right context
-
Git version history
-
An AI operating manual
PARTNER DATA
From partner notes to a usable list.
One structured file per partner or supplier becomes a filterable spreadsheet through a one-command export. The source records a verified run using synthetic demo data.
-
Partner directory and export
05 · TARGET AUDIENCE
For teams whose
context matters.
Independent professionals
Consultants, tax and compliance specialists, agencies and brokers managing recurring client context.
Multi-entity operators
People running related companies or brands who need a shared operating reference across their work.
Knowledge-led teams
Small teams organising country rules, partner information and sourcing references for human and assistant use.
Best suited to operators comfortable maintaining structured files. Hosted collaboration, permissions dashboards and multi-user editing are outside the demonstrated build.
06 · PRODUCT STORY
Not another
accounting platform.
WIKI starts with the details that make an operation work: how a client likes to be addressed, which reference is confirmed, and who needs to act next.
The source build ,provisionally named OpsVault ,combines a reusable architecture with a written operating method. Markdown keeps the records readable, templates give them consistency, and Git preserves their history.
Demonstrated in one real multi-entity business.
The source inspection reports roughly 300 Markdown pages and about 240 Git commits over approximately four months. The partner export produced a correct spreadsheet on synthetic demo data.
The portfolio presents that reusable method. Confidential client content is excluded. Records still need active maintenance; assistant-driven ingestion is guided by an operator, and live in-editor queries remain an optional, unverified addition.
07 · FAQ
FREQUENTLY ASKED QUESTIONS
What is WIKI?
WIKI is a structured knowledge and operations vault built from Markdown files and Git. Its Operations Registry holds client context; its Knowledge Base holds country and topic references and partner records. It runs on tools you own rather than a hosted software account.
Who is it designed for, and what tools are required?
It suits independent professionals, small services teams and operators managing several entities or brands. You need a Markdown editor such as Obsidian and Git. The partner export also requires Python 3, PyYAML and openpyxl. Basic familiarity with these tools or a scoped setup engagement is needed.
Can an AI assistant maintain the vault?
An assistant with local filesystem access can follow the operating manual to update records and draft replies. This guided method has been demonstrated in the reference build. It still depends on an operator and review; emails are not sent automatically. Live in-editor queries are optional and were not verified in the reference build.
Where does the data live, and what is available?
You choose where the files and Git history live and how they are protected. The confidential reference vault is not shared. A setup engagement can be discussed; a self-service starter template is a possible future package. Hosting, backups, support and maintenance require a separately agreed scope.