@ouronet/talos-registry 1.3.0 → 1.4.0

package/TOOLTIP-CANON.md

@@ -95,9 +95,21 @@ header comment. The claim had been *inferred* from "this is not an Ouronet opera
 nothing about who pays the host chain — and it was wrong in the direction that matters, telling a
 user they were about to spend when they were not.
 
-**Render native with a gold perimeter.** The gold is semantic, not decorative: it means *nothing
-here prices this call*. And say what is missing rather than leaving the cost panel empty — an
-empty panel reads as "the price failed to load".
+**Make the two visually distinct — the palette is yours.** The distinction is mandatory because
+the two differ in what they cost and what can be previewed; the specific colour is presentation,
+and this package does not get a vote on your design language. A rule that mandates a palette in
+someone else's application is a rule that gets ignored, and an ignored rule weakens the ones that
+matter.
+
+In practice:
+
+| | native (`coin.*`) | Ouronet (`ouronet-ns.*`) |
+|---|---|---|
+| OuronetUI | gold `#ceac5f` | blue `#3b82f6` |
+| Codex | *its own* | violet |
+
+Whatever you choose, make it carry meaning rather than decoration, and **say what is missing**
+rather than leaving the cost panel empty — an empty panel reads as "the price failed to load".
 
 Suggested footer, which is what OuronetUI ships:
 

package/dist/tooltip.d.ts

@@ -25,7 +25,15 @@ export interface TooltipPreview {
     call: string;
 }
 export interface TooltipModel {
-    /** `native` renders with a gold perimeter and no cost section -- rule 4. */
+    /**
+     * Which world this call belongs to -- rule 4.
+     *
+     * A renderer MUST make the two visually distinct, because they differ in what they cost and
+     * what can be previewed. It is NOT told how: OuronetUI uses gold for native and blue for
+     * Ouronet, the Codex uses violet, and both are conformant. Mandating a palette in a package
+     * consumed by applications with their own design languages would be the kind of rule that gets
+     * ignored, and a rule that gets ignored weakens the ones that matter.
+     */
     kind: "ouronet" | "native";
     /** fully qualified execution, as it would be typed in a transaction. */
     exec: string;

package/dist/tooltip.js

@@ -24,8 +24,8 @@
  *
  * 4. NATIVE IS NOT OURONET, and the difference is narrow. A `coin.*` call has no INFO_ preview
  *    and collects no IGNIS. Gas IS still sponsored -- claiming otherwise tells a user they are
- *    about to spend when they are not. Render native with a gold perimeter so the two are never
- *    confused, and say what is actually different rather than inventing a difference.
+ *    about to spend when they are not. The two MUST be distinguishable at a glance; HOW is the
+ *    implementation's choice. `kind` is the canon; the palette is not.
  *
  * 5. A GHOST IS NOT DATA. An unresolved argument must LOOK unresolved, and a tooltip whose
  *    arguments are placeholders must not fire the preview read at all: the answer is a foregone

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ouronet/talos-registry",
-  "version": "1.3.0",
+  "version": "1.4.0",
   "description": "The Ouronet callable surface, generated from the deployed contracts. Supply values; never type a function name.",
   "type": "module",
   "main": "./dist/index.js",