Fund Factsheet Page

Turn user-supplied fund factsheet points into one still per page. This fund factsheet page studio lays out each prospectus page still from the supplied fund factsheet. Use it for factsheet page graphics, fund page set layouts, and page-by-page fund stills.

Fund Factsheet Pages

Make one prospectus still per named page or step from facts the user already supplied. Use this Skill when a wealth session needs a page-by-page fund still set, not a four-to-eight product gallery and not a performance chart.

Use ecommerce-listing-image-set when the work is a hero, lifestyle, and detail gallery. Keep Amazon module packs for amazon-a-plus-module-pack when that package is installed. Do not look up public posts or market quotes for missing factsheet lines.

Collect supplied pages

Hard inputs are the exact fund name and the user-supplied factsheet page or step points that will appear on the stills. Do not invent a NAV, return, ranking, buy recommendation, risk grade, or fee line to finish a page. Reuse destination (handout, screen, print), language, and must-keeps already in the conversation.

Ask only for facts that change the pages:

• exact fund name;
• the page or step titles the user wants printed;
• the factsheet lines the user has already approved for each page;
• destination surface and language; and
• an optional brand still if the pages should match that look.

A scan or photo is a visual reference, not a source for missing numbers. Uploading makes media available to Beatra and does not inspect it. When the host cannot view a file, keep the user's declared role for it.

Default to one still per named page or step. Several pages are several stills, each with its own fact list. Omit a line whose fact is missing and keep that gap on the plan so the user can add it later.

Plan the free page list

Write a labeled page list before any paid image. For each page record the printed lines, language, layout (title, body points, optional footer), canvas, and any optional reference role. That list is the free visible result. Planning is not approval.

Before setting a concrete model, canvas, output count, or price, read the current beatra.models.list card for text_to_image. Keep model as auto and count at 1 per page. A user who wants another candidate adds a distinct page and approves that new work.

Use beatra.images.edit only after the user accepts a page and asks for a local correction, with that accepted image as images[0].

Read fund-page workflow when writing the payload or recovering a task.

Confirm once, create by page

Planning is free. Before the first billable call, show one current production card and wait:

1. Work — one prospectus still per named page or step, a generate call (beatra.images.generate).
2. Credits — the live text_to_image price just read. Do not reuse a remembered number.
3. Count — one paid call per page still. Do not batch several pages into one count.
4. Identity — one new opaque client_request_id per page. A changed prompt, fact line, file, model, or canvas mints a new ID.
5. If we stop here — the labeled page list remains usable.
6. If the balance is insufficient — relay the official message and its top-up URL exactly. Translate the prose; keep the URL. Do not retry until the user says they have topped up.

Submit once through bundled scripts/mcp_client.py. Poll beatra.tasks.get. Deliver actual bytes plus billing.net_charged_credits. Do not promise the prepaid estimate is the final charge.

After approval, submit each page once. Keep no more than two generation tasks in flight on one connection.

Review, deliver, and recover

Review printed lines against the confirmed page list. Report only the text the host can actually see. Treat generated small type as a review item, not as a certified disclosure.

Deliver the stills in page order, the page list, observed dimensions and formats, task IDs, resolved models, and returned billing.net_charged_credits. A focused correction is new paid work with its own card and ID.

After a returned task_id, poll that task. If the create response is lost, retry only the identical frozen payload with the original ID. If the task ID is missing, use beatra.tasks.list and verify candidates with beatra.tasks.get before another submit. Use beatra.tasks.cancel only when the user asks.

Execution

Invoke every remote Beatra operation only through this package's bundled scripts/mcp_client.py. Put the MCP tool name after call and send one JSON object on standard input.

bash

python3 scripts/mcp_client.py call beatra.models.list

json

{"capability": "text_to_image"}

text

printf '%s' '{"prompt":"Create the approved fund factsheet page still for the named page. Print only the confirmed factsheet lines.","model":"auto","count":1,"canvas":{"type":"preset","tier":"2K","aspect":"3:4"},"client_request_id":"opaque-fund-page-01"}' | python3 scripts/mcp_client.py call beatra.images.generate

Do not configure or call a host Beatra Connector, and do not use REST/OpenAPI as a fallback.

Account balance

When the user asks how many credits remain or whether a live estimate fits, call beatra.wallet.get. When they ask what was charged, call beatra.wallet.ledger. Both are read-only. Do not invent an account-balance or top-up tool. Do not make wallet.get a required step before every paid submit.

When a model card comes back carrying a top_up block, relay its tiers as the card lists them and in that order. Do not rank them, do not talk one down, and do not pick one for the user. Which tier suits them is their call, made on the wallet page with the whole list in front of them. Never quote a tier from memory.

References by task

• For page lists, payloads, confirmation, polling, recovery, and review, read fund-page workflow.
• For authorization and the non-billable registration step, read installation and authentication and installation registration.
• For shared task, billing, and connection details, read tasks and results, billing, errors, and recovery, and Bundled MCP Client diagnostics.
• For update guarantees and controls, read automatic updates and safety. For removal, read uninstall and disconnect.

Runtime and safe automatic updates

The bundled client silently checks for a newer release at most once every 24 hours per installation. When a newer version is available, it installs automatically without separate confirmation. It downloads only from the fixed official Beatra discovery and immutable CDN paths for this package, channel, and locale, verifies discovery data, archive, manifest, and every packaged file, and replaces only package-owned files.

Update checks, downloads, verification, replacement, rollback, and recovery fail open: the current installation remains usable and the original command continues. An update failure never authorizes retrying a paid image request. The setting persists for this installation. See automatic updates and safety.

text

python3 scripts/mcp_client.py update --auto off
python3 scripts/mcp_client.py update --auto on
python3 scripts/mcp_client.py update --check