Appearance
What the agent renders
Beyond asking for one field at a time, the agent can put a block on the page's stage. There are three, it may place at most one per turn, and everything in them is checked server-side before it reaches the page.
The five field actions
These are always available, to every bundle:
| Action | What happens |
|---|---|
set_field | A value is written into your real input, firing input, keyup, change and blur so your masks and validators run. |
ask_field | A control is drawn for one field — chips, a select past eight options, or a text box. |
focus_field | Your real control is focused and scrolled to. This is how the agent points at a locked consent box. |
submit | The confirm step, or an immediate submit under data-nam-submit="auto". |
complete | The conversation is over. |
The three stage blocks
| Action | Block | May share the turn with an ask? |
|---|---|---|
ask_field with a presentation | A question unit | It is the ask |
show_cards | Option cards | No — the cards are the control |
show_sheet | A plan, result or reflection sheet | Yes |
At most one of these reaches the page per turn. A second is dropped with a console warning.
Question units
When a choice field has help text, or any of its answers carries data-nam-image, the ask is drawn as a question unit rather than bare chips: a heading, the help line, "Question 2 of 4", and the answers as rows, image tiles or a scale.
Tapping an answer checks your real radio or sets your real select. See The fields for the markup.
Option cards
A set of up to four cards, each with a title, a "Why it fits" line, a few facts and a Choose button. Where the campaign's offer pools allow a partner offer, exactly one card can be marked Sponsored, carrying its own disclosure and a tracked link that is kept visually apart from Choose.
Two rules the platform enforces rather than trusts:
- Card links come only from an offer in the campaign's own pools. A URL the catalog does not know is stripped before the page ever sees it.
- Cards exclude a field ask in the same turn. The cards are the control. An ask sent beside them is dropped with one console warning.
Sheets
A plan, result or reflection the visitor can copy: a title, an optional cover, a summary, facts, up to six steps, a receipt of what they told you, a compliance note, and one link. A sheet may carry a field ask in the same turn, which is how the agent asks for a phone number beside the plan it just made.
Copy uses the clipboard where it is allowed and falls back to a selectable textarea where it is not.
Where the pictures come from
Images on cards and sheets come only from the materials registered for your landing page on the Namakina side, each with an id the agent writes. An unknown id is stripped before the page sees it, which means the agent cannot put an arbitrary image on your page even if it tries.
Pictures on answers are different: those are yours, from data-nam-image on the markup.
Capability advertisement
Every message the SDK sends carries its version and the list of blocks it can draw — cards, sheet, visual_ask, and panel when the layout is a panel. The agent is only offered what your bundle can render, so an older bundle on a page you have not redeployed degrades to the five field actions instead of rendering nothing.
If you see second stage block ignored or ask ignored beside cards in the console, that is the SDK holding the one-block-per-turn line. The turn still renders.