Patch your product into the company.
Connect anything you run — your site, your repo, your docs, your brand, your accounts. The company learns it on its own, asks you about whatever is unclear, and goes to work with exactly as much power as you grant. Nothing is taken. Everything is patched, source by source.
This is the only page in the family you operate rather than read. The switches below are the content.
At rest the board is dark — most jacks unlit. The one live cord is the page's only motion. A master kill switch can close the bridge at any time. (With scripting off, the board below is shown as a fully labeled static diagram.)
Connecting is granting, source by source.
Connecting a project never means handing over a key to everything. You grant a read scope over each source you choose — and only those. Pick what the company may look at; leave the rest dark.
The seven jacks
Each is a separate grant you can revoke at any time.
Brand assets means everything that shows your taste
Logos, decks, mood boards — the visual record of who you are. Analytics means the live numbers you choose to expose. MCP means any server or API your product already speaks, mounted read-only — your product's own tools, plugged in. The amber dots above are the only color here: they mark sources that feed manas, the memory.
Granted, not taken
Each jack is a read scope you hand over deliberately — a URL, a repo connection, an OAuth on a social account. The company sees only what you patched in.
Revocable any time
Pull a cord and the company stops learning from that source at once. What it already learned stays cited to where it came from, so you can see exactly what to forget.
Read first, always
A patched source is read-only. Granting a source never grants an action — outward acts live on the separate channel scopes, off by default.
The moment a jack is patched, the company starts learning it.
As soon as the bridge opens, manas's imbibers fan out over the granted sources and build the project's first Context Pack — who you are, your voice, your visual taste, your promises, your history. This runs continuously, not once: new docs, posts and comments keep flowing in, and the Pack ticks new versions. This is what makes deep audit possible — every later act traces back to a cited source.
The fan-out
The instant a jack is patched, imbibers crawl that source — your /about, your last forty posts, your deck, your roast-log — and start drafting the Pack. Each finding carries the source it came from, so nothing in memory is unattributed.
Pack v1 forms
Identity, voice, visual taste, promises, history — a first coherent picture of the company. arivu, the judge, grounds in that Pack plus the live numbers you granted from day one. Proposals can begin; nothing fires.
Versions keep ticking
New docs, posts and comments keep flowing in; the Pack ticks v2, v3, and on. The witness shows it happening live. The company is never frozen on a single snapshot of who you were the day you connected.
Sundara Coffee Co. — a coffee roastery
Nothing goes out yet — patching a source only lets the company read it.
- no sources granted yet — the Pack is empty
manas never guesses. It asks you.
When the Curator finds a contradiction or a gap, it doesn't invent an answer — it raises a question to you, as a card in saakshe right beside the gate queue. Answering teaches the company, with you as the cited source. Contradictions become onboarding, never bugs. Questions are batched and respectful of your attention — never a quiz, never blocking what can already run.
Your site says one price; your launch deck says another. Which is the live price?
Two logos are in circulation; your docs read formal, your social reads playful. Which voice is canon?
No refund policy is found in any granted source. What should the company tell a customer who asks?
An answer is a teaching, not a test
You are not being quizzed. A question only appears when the company genuinely cannot tell two granted sources apart, or finds nothing where it expected something. Pick the answer, type a line, or skip it for now — whatever can already run keeps running while the question waits.
Pressed into the record
Every answer commits to memory pressed with a nameplate — SOURCE: you, founder, with the date — so the audit trail always shows the company learned it from you, on a day, and did not invent it. The next time it matters, the answer is there with your name on it.
Swap the hands. The taste stays.
kalai, the studio, talks to creation backends through adapters. The first-party media MCP is the default — images, video, music, voice. But you can mount any backend you prefer: your own MCP server, another image API, a local pipeline.
The key architectural claim
kalai's taste layer is backend-agnostic. The Creative Director's direction, the Brand-Fidelity scoring loop, and the Compliance gate wrap around whatever backend generates the pixels or audio. Change the engine; the brand standard, the scoring, and the gate do not move.
What kalai never holds
kalai creates; it does not speak. It carries no channel keys and never publishes. When a piece is done, that is a handoff to kural, the only mouth — who only ever holds the scopes you granted on the next section.
Each channel patched separately, with four scopes you throw.
Every channel — X · Instagram · LinkedIn, more later — connects on its own keys, and carries four independent scopes you toggle. Any combination: post-only, listen-only, everything, nothing. kural only ever wields the keys you chose to hand it — and manas, not the mouth, custodies them.
The four scopes
- publish — send posts outbound.
- reply — answer comments outbound. Sensitive replies stay founder-gated.
- listen — read mentions and comments inbound, feeding manas.
- outreach — send DMs as you.
Throw them on the board
The live switches are in the demo above (section 03). Patch two sources to surface the question, answer it, then the channel strip appears with twelve real switches — four per channel — and a plain-words line that reacts as you flip them.
A safe default: every switch starts off. The company can learn and propose immediately, but nothing leaves a channel until you throw a switch.
Every control is yours. Safe by default.
A fresh connection starts read-only and fully gated — the company can learn and propose, but every outward act needs your tap, until you deliberately loosen it. Power is granted, never assumed.
Locked down & gated
- ›manas reads only the sources you patched — and learns continuously.
- ›arivu may decide and queue; nothing fires.
- ›kalai may create and score; nothing publishes.
- ›kural wields no channel keys — every scope off.
- ›every outward act waits in the gate queue for your tap.
Fully yoked
- ›sources granted across site, repo, docs, brand, social, analytics, MCP.
- ›scopes thrown per channel — publish, reply, listen, outreach.
- ›gate strictness set to auto-with-a-daily-digest on the reversible.
- ›spend caps set; the irreversible still gated.
- ›sensitive replies remain founder-gated regardless.
Every control, in one place
Master kill switch
The bridge can always be closed — one throw greys the whole board. Nothing learns, nothing acts, until you open it again.
Per-agent enable
Switch any one of the four — manas, arivu, kalai, kural — on or off independently. Let the company learn but make nothing; let it make but say nothing.
Per-scope toggles
Twelve switches across three channels — publish, reply, listen, outreach — each thrown on its own. The board in section 03 is the real thing.
Spend caps
A daily ceiling on what the company may spend on creation and outreach. Reach it and work pauses for your tap, never overruns it.
Gate strictness
Three settings, your call: gate everything · gate only the irreversible · auto with a daily digest. Loosen as trust grows; tighten in a breath.
Data boundaries
Mark what manas may and may not read, source by source. Revoke a jack and the company stops learning from it from that moment on.
It is up to you to use these or not. setu hands you every control; the company assumes none of them on its own.
The bridge stays open both ways. The witness records everything.
The company keeps learning, and saakshe, the witness, records which source taught it what, which permission allowed which act, and which tap approved it. The audit trail is the product's spine — not a feature. Every entry is pressed with a nameplate, so provenance is a physical artifact, not plain prose.
Inbound — the company keeps learning
New docs, fresh posts, the comments coming in through a granted listen scope — all of it flows back across the bridge into the Context Pack, which ticks new versions. The company you connected six months ago is not the company it knows today; it tracks who you have become.
Outbound — only through what you granted
Every outward act is checked against the scopes you threw and the gate strictness you set. Nothing leaves a channel it was not granted; nothing irreversible fires without a tap. The same trail that records learning records every act and the permission behind it.
What the four do with what you grant
absorbs every granted source into the Context Pack, continuously.
grounds every decision in that Pack plus your granted live numbers.
creates through your chosen backend; the taste layer stays the same.
speaks only through the channel scopes you threw — nothing more.
records the whole trail and lands your one tap on the gate.
Plainly: what is wired right now.
Today, the first-party media MCP is the wired creation backend, and your own accounts are the wired channels. The self-serve adapter layer — mounting any creation backend you like — and the channel connectors as a productized, self-serve step are the work ahead. The architecture above is real and backend-agnostic by design; the productization is the next step, and we are saying so directly rather than implying it already ships.
- the first-party media MCP as kalai's creation backend — images, video, music, voice.
- the founder's own accounts as kural's channels.
- the consent board, gates, and the audit trail — the spine, real now.
- the self-serve adapter layer — mount any creation backend you prefer.
- channel connectors as a self-serve product — bring your own keys, any platform.
- the design holds the difference today; the connectors are the next build.