What it is
Upload your company’s coding standards once, and every ARVO Studio project follows them. ARVO sends the active documents with every AI call that designs or writes code: technical architectures, technical designs, code generation and compile repairs.
Business skills work the same way for your company’s know-how and ways of working. Each skill goes with the compass steps you choose for it.
A document never overrides ARVO: a value set in a field of ARVO Studio Setup or of a project, and ARVO’s built-in rules, always win.
Turn it on
- Open ARVO Studio Setup. In the Standards & Skills group, turn on Use Coding Standards, Use Business Skills, or both. While a switch is off, ARVO works exactly as it did before.
- Every project follows them from then on. To leave one project out, open its project card and turn the switch off on the Standards & Skills tab.
Projects that existed before the feature arrived show the project switch off until you tick it.
Upload, new versions, retire and order
Open the ARVO Studio Coding Standards page from ARVO Studio Setup, from the Standards & Skills tab of a project card, or with Tell Me.
| Action | What it does |
| Upload | Adds one or more Word (.docx), Markdown (.md) or text (.txt) files. Each is active from the next run. |
| Upload New Version | Makes the file the next version of the selected document, whatever the file is called. The version before is kept as Superseded. |
| View | Shows the document as the AI reads it, under What the AI Reads. |
| Retire | Takes the document out from the next run. Runs that carried it keep it on their record. |
| Move Up / Move Down | Sets the order the AI reads the documents in. Where two disagree, the earlier one wins. |
| Download | Downloads the file a version was uploaded from. |
When you upload a file with the same name as an earlier document, ARVO asks whether it is that document’s next version, a separate document, or one to skip. A file that reads exactly like the active version makes no new version.
A version that a run carried can’t be deleted: it stays as that run’s record. Retire it instead.
Conflicts
ARVO lists every place where a document disagrees with a field or with one of its built-in rules. The field or the rule always wins, and the list shows what the document says next to what ARVO does.
Conflicts are found two ways:
- On upload. ARVO reads each document, with no AI, for topics a field decides: the object prefix, the object id range, permission sets, API pages, Role Centers, the publisher, app.json, and translations. It also flags documents that ask for permission checks in code (ReadPermission or WritePermission), which ARVO’s built-in rules forbid.
- By code generation. When the AI could not follow a standard, it says so, and the line shows Found By Code generation with the run number.
Conflicts on the page lists the documents in effect. An earlier version keeps its own list: open that version and choose Conflicts there.
Business skills
Business skills are uploaded on the Business Skills page the same way as coding standards: open it from the Business Skills value in ARVO Studio Setup, or from Company Skills on a project card.
On each skill, tick the compass steps it is sent with: Solution Requirements, Requirements, Solutioning, Personas, FDDs, Training, TDDs, Test Cases, Data Plan, Generate, Build, Configure Data, Test App, Execute and Ask ARVO. The active version’s ticks count, and a new version keeps them.
ARVO’s rules, the project’s settings, the solution requirements and the approved designs always win over a skill. Skills are not checked for conflicts.
See what a run used
Every run records which version of each document it carried, so a later upload never rewrites what an earlier run was told.
- The run’s checkpoint trail has a line such as coding standards: 1 document(s) carried – Harbourline AL Coding Standards v2.
- The receipt lists STANDARDS IN EFFECT, with who uploaded each version and how many deviations code generation reported, and SKILLS IN EFFECT.
- The pull request in GitHub lists the coding standards in effect, and ARVO writes them into a standards file for Copilot’s review.
A project linked to a GitHub repository can also follow the rule files its developers keep there. See GitHub Repository Coding Rules.