Foundation

Foundation is the shared product brief for your team and agents. It describes what you sell, who it helps, features, plan differences and important limits. New drafts use its active revision; existing emails are not rewritten.

Add and edit product knowledge

Product details are grouped into expandable sections. You can open several sections at once, or use Search product details to find a statement, plan, category or source. Matching sections open automatically. Each entry keeps its statement, plan and source together in one compact list row.

Each section has an Add entry button, including Features. Each entry has its own Edit button. Open its More actions menu to remove it. You can also use Add product knowledge to choose a section for a new entry. Empty sections stay visible so you can start adding information.

UI entries are saved directly as Manual entry, in your exact wording, without an AI request or individual approval. Entries accept up to 600 characters. Edits retain the existing entry key and category and take priority over matching website or agent claims. Stale extracted values and plan badges are cleared when you rewrite an entry, so old metadata cannot contradict your new statement. Remove withdraws an entry from the active brief; source history stays in earlier revisions, and a later website refresh cannot bring that claim back until you add it again. Other entries stay unchanged. Every change creates a Foundation revision. Manually added entries are active immediately; there is no coverage review or additional approval step. The counts beside sections show stored entries, not pending reviews.

The summary at the top has a separate Edit button and accepts up to 1,000 characters. It is also saved as written, without changing the entries below. There is no global product knowledge editing button.

Expand Source & evidence to see the original excerpt. Sources & contributions retains source attribution and original contributions. UI edits are recorded on a shared team contribution (ui:team) with manual origin and the author of the revision.

Failed saves preserve your text. If another update changes the revision while you edit, load the current knowledge, compare it with your text, and reconcile before saving. No existing emails are rewritten.

Connect sources

Connect a public homepage, pricing page, help page or App Store listing. Audryo reads that page and adds its evidence to a revision automatically. After the first read, Audryo suggests follow-up pages it found on the site (pricing, help/docs, app stores) so you can deepen the brief in one click. Refresh checks the source again. Unchanged text does not trigger another extraction. This release does not crawl a whole help center or schedule recurring refreshes; connect the specific pages you want to use.

A failed source does not replace the active product brief. Removing a source withdraws its contribution from current knowledge; historical revisions retain it for traceability. Your other sources and team notes remain.

Unclear information

When sources produce different values for the same extracted claim key, Audryo keeps the alternatives in the revision but excludes that claim from generated email copy. Unclear availability is handled the same way. In the product knowledge UI, choose one alternative or write your own clarification; that manual statement takes priority for the matching claim. Semantic key matching is model-assisted, so this is not a guarantee that every contradiction in arbitrary prose will be detected.

Availability and beta restrictions stay in the statement. A source containing code for a feature does not establish that every customer can use it. Missing prices or plan entitlements are not filled in by guessing.

Agent updates

With the hosted MCP server, use get_foundation, update_foundation and restore_foundation. HTTP clients read GET /v1/projects/{projectId}/foundation. Prefer structured patch updates for precise changes. Send a stable sourceKey, mode: "patch", ops, and the returned revisionToken as a quoted If-Match header:

POST /v1/projects/{projectId}/foundation/contribute
Authorization: Bearer <workspace-token>
If-Match: "<revisionToken>"
Content-Type: application/json

Patch merges into that source only, does not call the model, and preserves other sources and UI notes. Use free-text mode: "contribute" (default) when syncing a full document; that replaces the source's complete contribution after extraction, so include every statement that should remain in it.

{
  "contribution": {
    "sourceKey": "juno-api",
    "content": "Voice recordings last up to 600 seconds. They are currently enabled only for selected beta families.",
    "changeSummary": "Updated voice recording limits and beta availability.",
    "references": ["app/models/audio_recording.rb", "app/models/family.rb"],
    "release": "<git-sha>"
  }
}

Requires read to inspect and write to update. No deliver scope or per-fact approval is needed. References supplied by an agent are attribution, not files fetched by Audryo.

The initial token is 0. Missing or stale preconditions return 412; read the new revision and reconcile before retrying. Identical patch results or identical contribute content, references and release are a no-op. Agent source keys cannot use the reserved ui:, web: or legacy: prefixes (including ui:team). Contributions accept at most 30,000 characters, 50 patch ops and 20 source references; a Foundation supports up to 40 source contributions and 500 manual entries on the shared team contribution.

Revisions

Revision history shows who updated the Foundation and the change summary. Restore an earlier snapshot to create a new active revision; history is retained. Agents can use POST /foundation/restore with revisionId and If-Match. Restoring does not undo product deployments or modify existing emails. A later explicit source refresh can reintroduce newer information.

Existing confirmed facts are carried into the first revision. In product_context, foundation.current becomes authoritative, profile is its summary projection, and the legacy facts array is empty so older claims are not mistaken for current knowledge. Legacy individual fact/profile edit endpoints return 409 foundation_revision_required once a Foundation revision exists; use contributions instead.

Brand kit

The brand kit holds your logo, colors and fonts. It remains independently editable and is initially extracted from your website. New emails use the brand base template. See Templates and brand.

Related

• Quickstart
• Templates and brand
• Design emails with your agent