ARCY AI

Procedures

Read the Procedures ARCY drafted and what each needs from your product, publish one, try its samples in the Preview, and read the nightly check.

Procedures holds what ARCY does for your visitors, one job each. A Procedure is a page of plain language in your product's own words, plus four controls ARCY cannot step outside. Nothing runs for a visitor until you have read it and pressed Publish.

Before you start

  • ARCY drafts up to six Approved Procedures after your Reports (Home), and one more when three visitors in a week asked for a job no Procedure covers (Conversations).
  • The Preview needs no Domain. Play sample (Development environment) on your own site needs a verified Domain covering it, with arcy.js installed.
  • Reading is every member's. Approve, Publish, editing and Delete Procedure are an admin's.

Setting it up

Each row carries a status, Draft, Approved or Live, what it runs on, and when it was Created and Updated. A pill beside the status shows only when the row needs a look: Cannot run or a count of what your product still lacks. Every night ARCY plays each Live Procedure's sample visitors on your Development site; a row whose last check failed reads Stopped holding beside its status. A Procedure a coding agent proposed over ARCY MCP waits in Proposed by your agent above the table: Changes a Procedure lists what Accept rewrites and keeps it on or off; Adds a Procedure lands Approved. New Procedure asks What should ARCY do for your visitors?; one sentence and Draft it make a Draft row with up to eight sample visitors.

Open a row to read it. The Instructions are what ARCY follows, 5,000 characters at most. A drafted text holds a section per situation: done, not eligible, each write outcome, a missing value, hand-off, a neighbouring request, what comes next. Insert, or /, lists your Product's Operations, Attributes and Events and writes the one you pick; an Operation also joins the operations control. One save bar, Save changes or Discard, holds the Instructions and the controls. Under it, the controls, each with Edit: the operations ARCY may call, what it must read first, what it must know before acting, when it hands the visitor to a person, and what counts as done. An operation named here is one of your Endpoints; a Procedure naming none runs through your pages. Add Operation searches by name. Buttons and fields it may use on the page lists what ARCY may click or fill, typed as the page shows them.

Fixed rules is a row only a Procedure that holds some shows. Your coding agent proposes each from your code, and you read it as a sentence: before a change, if a field in a read's answer has a value, ARCY stops, passes the visitor to a person, or goes to another operation instead, and says why. ARCY applies it the same way on every run, never by judgement. Edit removes one; Save changes keeps the rest. Accept refuses a rule naming a field the read does not answer with. Press a write's row for Approval question, Result sentence and Person key (the record field naming who a send reaches, empty on every other write) hold what the visitor reads, in your agent language; other languages are on the Localization tab of Appearance, and a blank field reads ARCY's neutral words. A menu under them names the cleanup the nightly check calls after that write; No cleanup keeps the check read-only there.

Under the controls, To make this work lists what your product lacks: Needed, read in your code by your coding agent, To check, which ARCY only guessed, Ready when your product is connected, and Already in your product. Copy the prompt for your agent hands the list over. Until a needed endpoint exists, the readiness line reads Needs 1 thing from your product. Two operations asking for the same kind of value under different names are listed under Asked twice, so your agent gives both one meaning.

Under the two pills, a Live Procedure says when the nightly check last held; one that did not shows Stopped holding last night with the sample, the failed checks and, where ARCY wrote one, ARCY proposes a fix: the revised text and its reason. Approve fix replaces the text and the next night checks it again; Dismiss clears it. A Procedure drafted from your conversations says how many asked, and See them opens them.

History in the header lists every change, newest first: what made it, who, when and the fields it moved. Restore puts back the version before that change, and is a change itself, so it can be undone. Publish and Unpublish are not changes, and other languages keep their own text. The last 50 are kept, and deleting the Procedure deletes them. A failed check names the newest change before it, to the Procedure or to an Operation it uses, with Open the history.

Preview in the header opens, in a drawer, the chat panel a visitor gets, on your Development environment; Expand widens it, Refresh restarts it. The samples above it each put their first message in the chat box when pressed; nothing is sent until you send it, nothing in the panel counts as a visitor. A Procedure that writes runs as a test visitor: with none stored, the panel asks for Test visitor, a cookie or bearer token from a test account, and Save test visitor keeps it encrypted. A run reaching its done condition marks it watched; Publish never waits.

A step on your page shows in the panel as a link. A Procedure that acts on your pages has Play sample (Development environment), opening your Development site in a new tab for thirty minutes.

Publish makes it Live; Unpublish takes it back to Approved. A Draft shows Approve instead.

The nightly check's one switch, Nightly check writes on Development, is on Product. Off, a write stops at its approval card. On, ARCY says yes on Development to a write whose operation names a cleanup, then runs the cleanup; a write with no cleanup still stops at its card.

What it changes

  • ARCY picks among Live Procedures when a visitor writes. It never calls an operation the Procedure does not name, never writes before its required reads, and asks for what it must know first.
  • Editing a Live Procedure applies on save.
  • The nightly check never changes a Procedure on its own: a failed check is a line on Home and a proposal on the page until you decide.

When it goes wrong

  • A Preview runs on your Development site. Add a Development Environment first. The Product has no Environment named Development.
  • ARCY could not write a Procedure from that. Say what the visitor wants and what should happen.
  • This Procedure names an Operation the Product does not have. Add the Endpoint first, or take it out under Edit.
  • This version names an Operation the Product no longer has. Restore refuses it. Add the Endpoint again first.

See also

On this page