iSolomonDownload

Bringing the wisdom of the ages

An agent that reads your systems and shows its work.

iSolomon is not a chatbot. It reaches into the systems you already run, answers with figures you can trace to the record, and stops at your boundary. You stay in the chair.

Be the person at the consoleDownload the iSolomon Agent
  • Every figure traceable to a record
  • Read-only until a person says otherwise
  • One client, one boundary, no path across
The iSolomon plaza: the Healthcare billboard, the arch, the Media CenterThe PlazaWalk in →

The console

Try it before you read another word.

Three questions from iSolomon’s own world. Pick one, watch the work happen, press any figure to see where it came from, push back, and then try to make it cross into another client’s data.

iSolomon · ConsoleDemonstration · fictional data · scripted

Ask it something

Pick a question. You will see which agent picked it up, what it reached into, what it found — and then you can push back.

Three doors

Where iSolomon already works.

Louisiana HealthcareMyVerna, KOKO the healthcare robot, the Game of Health, and the LA Healthcare app.Media CenterPodcasts, video, and the record of what iSolomon has said in public.The PlazaWalk in. Meet iSolomon in the Portal room, then take the chair.

How it works

Two foundations and a person.

01

It reads. It does not guess.

Through MCP, iSolomon reaches into the systems you already run — records, calendars, documents, accounting — read-only until a person with authority says otherwise. Nothing is copied out. Nothing is written without a hand on it.

02

Every figure has a door.

The Graph Foundation holds what it read as people, records, places, coverage, and workflows, joined by named relationships. An answer is a path through that graph, and you can walk it back to the record it came from.

03

The line holds.

One client, one graph, one boundary. There is no path from your question to anyone else’s data, and none can be made. Agents do not delete and do not overwrite; a change needs a person with authority.

04

You stay in the chair.

An experienced person forms the question, guides the work, pushes back, and decides when the answer is right. That is the whole design. The agents do the reaching; the person does the deciding.

For you

Two readers arrive here. Both get an answer.

I run the business.

You want the figure, the reason, and the next thing to do — in the time it takes to ask. iSolomon answers the question you asked, shows the records behind it, and takes the follow-up. Nothing to learn, nothing to configure, nobody on your team retrained.

Ask it something

I run the systems.

Access granted
Read-only connections to named systems, scoped per client. Writes are a separate, explicit grant.
Isolation
One graph per client. No shared index, no cross-tenant path, refused by construction, not by policy.
Change control
Agents do not delete or overwrite. A change needs a person with authority, and the record of it stays.
Your part
You do not build the AI layer. You grant access, review the scope, and hold the keys.

Working together

Every engagement begins with a conversation.

  1. 01

    Discovery

    What you are exploring, who would sit at the console, which systems are involved, what a good outcome looks like.

    You: an hour with the people who know the work.

  2. 02

    Scoping

    A short written scope: the systems, the access, the boundary, the first questions the console will answer.

    You: read it, correct it, sign it.

  3. 03

    Integration

    Read-only connections, the graph built from your records, the first answers checked against the source.

    You: grant access; nothing else.

  4. 04

    Training

    The person who will sit at the console learns to ask, push back, and trust what they can trace.

    You: the person in the chair.

  5. 05

    Refinement

    The console grows with the questions you actually ask. Improvements arrive in place; nothing is re-tooled.

    You: keep asking.

Start at the consoleWalk the plaza