> For the complete documentation index, see [llms.txt](https://jordan-7.gitbook.io/jordan-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jordan-7.gitbook.io/jordan-docs/internal/briefs.md).

# Daily briefs

Plain-English end-of-day summaries for the project owner catching up after a day away. **Not written for engineers.** If a brief needs the reader to know what a webhook is, it has failed.

Any agent can be asked to write one: *"write today's brief"*.

## Convention

* **One file per working day**, named `YYYY-MM-DD.md`.
* **Plain English, no jargon.** Readable by someone who has never opened the code. Name the thing that broke and what it cost, not the module it lived in.
* **Short.** The value is that it stays short. Resist adding detail — the detail already lives in `OPEN-ISSUES.md`, `DECISIONS.md`, and the `HANDOFF-*.md` files.

### Sections, in order

| Section                              | Contains                                                                               |
| ------------------------------------ | -------------------------------------------------------------------------------------- |
| **Objectives**                       | What the day was for. One line each.                                                   |
| **What happened**                    | Outcomes, not activity. No commit logs, no gate counts.                                |
| **Problems and how we handled them** | Including problems still unresolved — a brief that only lists wins is not a brief.     |
| **Outstanding**                      | Split by who acts: owner vs engineering.                                               |
| **Outlook**                          | An actual call — **bearish / mid / bullish** — with reasoning, and what would move it. |

### Rules that matter

* **Say what is believed vs what is shown.** "Fixed and verified against a local test server" and "verified in production" are different claims and the brief must not blur them.
* **Keep bad news in.** A brief the owner can't trust to surface problems is worse than none.
* **Owner actions get a time estimate.** "Two minutes" is actionable; "configure webhooks" is not.

Where a day's brief was prompted by a specific request worth preserving, keep it alongside as `YYYY-MM-DD.request.md`.

## Index

* [2026-09-05](/jordan-docs/internal/briefs/2026-09-05.md) — guest list built and gated; a money check that was passing for a bad reason, and seventeen older tests found to be unreliable.
* [2026-07-25](/jordan-docs/internal/briefs/2026-07-25.md) — LiveKit cost leak found and fixed; bounty mechanic built; Cloud verification still outstanding. ([request](/jordan-docs/internal/briefs/2026-07-25.request.md))


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://jordan-7.gitbook.io/jordan-docs/internal/briefs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.