AI needs context

The nervous system for autonomous work.

In most companies, AI stops at contract templates, brainstorming and polished slides. Not because the models are too weak, but because they do not know how your company works. spinie connects documentation, processes and responsibilities into one system on which agents can take on real work.

Discuss a pilot Why AI stalls today

Knowledge becomes a nervous system.

What an agent needs for it

Documentation
Warranty terms and the service manual, in their current version.
Processes
The complaints procedure: check the entitlement, propose a remedy, obtain approval.
Responsibilities
The service lead approves goodwill above the set limit.
Permissions
The agent sees this customer's orders, but not purchase prices.
Connected systems
The ticket history and the customer record from the CRM.

The agent prepares the reply and the proposed remedy, cites its sources and hands over for approval.

What an agent needs for it

Documentation
Product data sheets and the current price list.
Processes
The quoting procedure, including the cases that require a technical review.
Responsibilities
Sales owns the quote; special discounts are decided by the head of sales.
Permissions
Price rules are visible to sales, not to every department.
Connected systems
Previous quotes and open opportunities from the CRM.

The agent drafts the quote from the customer's history and flags what still needs a decision.

What an agent needs for it

Documentation
Role description, tool guides and the team's working agreements.
Processes
The onboarding plan for the first weeks, step by step.
Responsibilities
Who grants access, who acts as mentor and who holds the probation review.
Permissions
New colleagues see what their role may see from day one.
Connected systems
Open onboarding tasks from the ticket system.

The agent guides the new colleague through each step and answers questions with the source attached.

Illustrative examples. What agents can take on in your company is something a pilot shows.

Why AI stalls at templates and slide decks

Even a capable new hire achieves little on the first day. They do not yet know how things are done here, who decides what, or where the reliable information is. In most companies, AI never gets past that first day.

Without that context, AI can

  • draft a contract template
  • collect ideas for a campaign
  • polish a presentation

Connected to how the company works, agents can

  • take a complaint from receipt to a proposed remedy
  • prepare a quote from the customer's history and the current price rules
  • guide a new colleague through the first weeks

The difference is not a better model. It is what the model is connected to.

Autonomy needs rules that hold

The more an agent is allowed to do, the more it matters what it may see and who has the final say. In spinie, these rules are part of the foundation, not an afterthought.

One set of permissions

People and agents are subject to the same access rules: in the interface, in search, via MCP and through connectors. Protected content does not surface in search results, in the context passed to a model, or in exports.

Every source traceable

Whatever an agent draws on carries its source, version and date. You can check what an answer or a proposal is based on.

Documents are data, not commands

Content from files and external sources is treated as untrusted. A sentence hidden in a PDF cannot change an agent's instructions or its access rights.

Described is not executed

spinie describes processes, including the points where a person decides. It does not carry them out on its own. Which steps an agent may take is defined explicitly.

Models change. Your nervous system stays.

What spinie holds is not tied to any single AI provider. Access runs through MCP, an open standard through which compatible agents and applications work on the same foundation.

Interchangeable models

Provider-specific functions sit behind adapters. Switching the answer model does not require your documents to be reprocessed. A change of embedding model is coordinated with the search index.

Export and re-import

Content, metadata and links can be exported in a documented format and imported again. You can leave spinie without leaving your company's context behind.

We name compatible models and applications only after an actual integration test.

Fed by the people who know the work

How the work is really done is known to the people who do it. They need to be able to record it without technical help.

Add
Upload a file or write down directly how something is done. You can see what is being processed and when it becomes available.
Update
Edit content without losing the previous version. Every change is a version, and every item has an owner.
Find
Ask a question and get the relevant passages: not just the document, but the section within it.
Trace
Every result shows its source, version and date, so you can verify what an answer is based on.

Error messages say what happened and what to do next. Infrastructure details stay out of everyday work.

Development status

spinie is under development. This list shows what you can use today and what is not yet available. We update it as soon as a capability has been verified. spinie provides the foundation; the agents that work on it are the applications you connect.

Capability Status
Upload files and capture knowledge as articles Planned
Edit and version content, and assign owners Planned
Search content and show results with their source Planned
Map process steps and responsibilities Planned
Connect additional sources via connectors Planned
Give agents access to the same foundation through MCP Planned
Export and re-import content, metadata and links Planned

Fewer subscriptions, if the assessment supports it

Wiki, document storage, search tool, AI assistant: many companies pay for several products with overlapping features, each holding a fragment of how the company works. spinie brings those fragments together in one place.

We do not make a blanket promise that a subscription can be cancelled. We assess it with you against two questions: which of the product's features do you actually need, and has the content been migrated successfully?

Start with a pilot

A pilot shows, with your content, your processes and your people, whether spinie holds up. We set out the criteria in advance.

View the pilot and its success criteria