> For the complete documentation index, see [llms.txt](https://wiki.fridays.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.fridays.bot/readme.md).

# Fridays: Approval-Gated AI for SMB Back Office

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask a question...</button>

> 🎯 **The thesis in one line:** an autonomous back office is only safe to sell to small businesses if every consequential action is bounded, cost-capped, auditable, and gated by a human — so Fridays puts a deterministic control plane *outside* the model and lets the model only plan, never unilaterally act.

&#x20;

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td>Every money- or identity-moving action stops for one human tap — the model can request, never unilaterally act.</td></tr><tr><td>A hard spend ceiling is enforced before any model call, so a runaway agent can't run up your bill.</td></tr><tr><td>Every action, decision, and dollar is a database row, not a log line — reconstructable after the fact.</td></tr></tbody></table>

❓ FAQ

Short, technical answers to the most common questions — what's built, how approvals work, how data and credentials are handled, and the compliance posture.

**Read the FAQ →**

### 🚧 What's built vs planned

Fridays is built on an open-source (MIT) orchestration control plane that runs today; the connectors, the hosted product, and the compliance program are in progress. The whitepaper labels every capability **EXISTS / PLANNED / ASPIRATIONAL**, and each section's As-Built Reconciliation ties the paper's architecture back to the shipped code. Start with §2 System Overview for the honest current-state summary.&#x20;

&#x20;

&#x20;

&#x20;

&#x20;

&#x20;

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.fridays.bot/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
