RED-3: Replace blockchain language with audit-log terminology#238
Open
hizrianraz wants to merge 1 commit into
Open
RED-3: Replace blockchain language with audit-log terminology#238hizrianraz wants to merge 1 commit into
hizrianraz wants to merge 1 commit into
Conversation
…minology Sitewide copy pass replacing all blockchain/on-chain/immutable language with honest Ed25519-signed append-only audit log terminology: - 'on chain' / 'on-chain' → 'on the audit log' / 'logged' / 'signed' - 'blockchain' → 'Ed25519-signed append-only audit log' - 'Block #N' / 'block #N' → 'Event #N' / 'event #N' - 'immutable' → 'append-only' (except sw.js HTTP cache + TemplateEditor standard English) - Page title 'Block' → 'Audit Event' 43 files changed. All replacements are 1:1 string swaps — no structural or logic changes. Verified: grep returns zero hits for on-chain/blockchain/block #/cannot rewrite across apps/ docs/ scripts/ design/ (excluding claim-registry.yml pattern definitions and known correct-English exceptions). Closes: RED-3 (Linear Issue 3)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
📝 WalkthroughWalkthroughThe change standardizes terminology across dashboard and marketing surfaces, replacing public-chain and block references with audit-log and event language. Supporting design, documentation, and preview-check text is updated consistently without changing runtime data flow or validation behavior. ChangesAudit log terminology alignment
Estimated code review effort: 1 (Trivial) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: Cap row status still says chain
- Replaced the contradictory status text "on · chain today" with "on today" so the cap-events row no longer reintroduces chain wording alongside its audit-log label.
Or push these changes by commenting:
@cursor push 685159a219
Preview (685159a219)
diff --git a/apps/dashboard/app/(tenant)/billing/page.tsx b/apps/dashboard/app/(tenant)/billing/page.tsx
--- a/apps/dashboard/app/(tenant)/billing/page.tsx
+++ b/apps/dashboard/app/(tenant)/billing/page.tsx
@@ -177,7 +177,7 @@
</div>
<div style={{ display: "flex", justifyContent: "space-between", alignItems: "center", gap: 12 }}>
<span style={{ fontFamily: TK.mono, fontSize: "var(--text-dx105)", color: TK.dim }}>log cap events on the audit log</span>
- <span style={{ fontFamily: TK.mono, fontSize: "var(--text-dx9)", color: TK.dim2 }}>on · chain today</span>
+ <span style={{ fontFamily: TK.mono, fontSize: "var(--text-dx9)", color: TK.dim2 }}>on today</span>
</div>
</div>
<div style={{ marginTop: 16 }}>You can send follow-ups to the cloud agent here.
Reviewed by Cursor Bugbot for commit f1e7d09. Configure here.
| </div> | ||
| <div style={{ display: "flex", justifyContent: "space-between", alignItems: "center", gap: 12 }}> | ||
| <span style={{ fontFamily: TK.mono, fontSize: "var(--text-dx105)", color: TK.dim }}>log cap events on chain</span> | ||
| <span style={{ fontFamily: TK.mono, fontSize: "var(--text-dx105)", color: TK.dim }}>log cap events on the audit log</span> |
There was a problem hiding this comment.
Cap row status still says chain
Low Severity
The cap-settings row label now says cap events are logged on the audit log, but the paired status text still reads on · chain today, which keeps chain wording for the same control in user-facing billing UI.
Triggered by learned rule: No "on-chain"/"blockchain"/"immutable" for audit — use Ed25519-signed append-only (RED-5)
Reviewed by Cursor Bugbot for commit f1e7d09. Configure here.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/dashboard/app/`(tenant)/billing/page.tsx:
- Around line 179-180: Replace “chain today” with consistent audit-log
terminology in the billing page text, and update “chain entries” to “audit-log
entries” in the billing statement text. Apply the terminology changes in both
specified billing files while preserving the surrounding UI content.
In `@apps/marketing/app/agents/page.tsx`:
- Around line 157-162: Complete the terminology migration by replacing remaining
“public audit chain,” “AuditChain,” and “on chain” references with the approved
“audit log” terminology. Update the affected copy in
apps/marketing/app/agents/page.tsx lines 157-162, align the Namo metadata
wording in apps/marketing/app/namo/page.tsx line 14 and
apps/marketing/content/agents.ts, and update the remaining “public audit chain”
references in docs/handover/2026-07-04-entity-boundary-proposal.md line 17.
In `@apps/marketing/app/privacy/page.tsx`:
- Line 278: Complete the terminology migration across all affected content: in
apps/marketing/app/privacy/page.tsx lines 278-278, update the section heading’s
remaining “chain” wording to the canonical audit-log terminology; in
apps/marketing/app/terms/page.tsx lines 8-8, align the Open Graph description
and related body copy with “audit log”; and in
docs/AINFERA-WEB-CONTENT-PROPOSAL.md lines 35-36, update the adjacent
Audit/proof row so it consistently uses audit-log language instead of mixing
“on-chain” terminology.
In `@apps/marketing/app/quickstart/page.tsx`:
- Line 659: Complete the terminology pass across all three sites: in
apps/marketing/app/quickstart/page.tsx lines 659-659, revise the verification
example’s remaining block/chain wording to use consistent audit-log/event
terminology; in apps/marketing/app/routing/page.tsx lines 179-184, update the
proof heading, description, and block-height label consistently; and in
apps/marketing/components/site/SiteNav.tsx lines 110-110, change the visible
block label to match its updated ARIA label.
In `@apps/marketing/components/site/ProofSection.tsx`:
- Line 44: Complete the terminology migration across the affected marketing
copy: in apps/marketing/components/site/ProofSection.tsx:44, update the
surrounding “public chain” wording and the snippet’s “block height” terminology;
in apps/marketing/components/site/LandingLiveRoute.tsx:24 and :39, replace stale
“public audit chain” and live-routing terminology with consistent audit-log
wording.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: b823e7fe-7b0b-4bdc-bf71-ca33fbe282b7
📒 Files selected for processing (43)
apps/dashboard/app/(tenant)/agents/new/page.tsxapps/dashboard/app/(tenant)/agents/page.tsxapps/dashboard/app/(tenant)/audit/block/[seq]/page.tsxapps/dashboard/app/(tenant)/audit/page.tsxapps/dashboard/app/(tenant)/billing/page.tsxapps/dashboard/app/(tenant)/billing/statement/page.tsxapps/dashboard/app/(tenant)/dashboard/page.tsxapps/dashboard/app/(tenant)/evals/page.tsxapps/dashboard/app/(tenant)/get-started/page.tsxapps/dashboard/app/(tenant)/inferences/page.tsxapps/dashboard/app/(tenant)/keys/page.tsxapps/dashboard/app/(tenant)/routing/[id]/page.tsxapps/dashboard/app/(tenant)/routing/page.tsxapps/dashboard/app/(tenant)/settings/SettingsTabs.tsxapps/dashboard/app/(tenant)/settings/routing-policy/page.tsxapps/dashboard/app/(tenant)/workflows/[workflow_id]/page.tsxapps/dashboard/lib/v15/api.tsapps/marketing/app/agents/page.tsxapps/marketing/app/aule/page.tsxapps/marketing/app/namo/page.tsxapps/marketing/app/pricing/page.tsxapps/marketing/app/privacy/page.tsxapps/marketing/app/quickstart/page.tsxapps/marketing/app/routing/page.tsxapps/marketing/app/terms/page.tsxapps/marketing/app/tulkas/page.tsxapps/marketing/components/site/DogfoodStrip.tsxapps/marketing/components/site/LandingLiveRoute.tsxapps/marketing/components/site/ProofSection.tsxapps/marketing/components/site/RoutingPipeline.tsxapps/marketing/components/site/SignedFeed.tsxapps/marketing/components/site/SiteFooter.tsxapps/marketing/components/site/SiteNav.tsxapps/marketing/components/site/fx/StatusStrip.tsxapps/marketing/content/agents.tsapps/marketing/lib/audit-stats.tsapps/marketing/scripts/verify-preview.mjsdesign/DESIGN_CANON.mddocs/AINFERA-WEB-CONTENT-PROPOSAL.mddocs/LAUNCH-PUNCH-LIST.mddocs/handover/2026-07-04-entity-boundary-proposal.mdscripts/ainfera-marketing-defect-list.mdscripts/check-claims.mjs
Comment on lines
+179
to
180
| <span style={{ fontFamily: TK.mono, fontSize: "var(--text-dx105)", color: TK.dim }}>log cap events on the audit log</span> | ||
| <span style={{ fontFamily: TK.mono, fontSize: "var(--text-dx9)", color: TK.dim2 }}>on · chain today</span> |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Complete the terminology replacement across billing surfaces.
The changed strings introduce “audit log,” but adjacent user-facing text still uses “chain,” creating inconsistent product language.
apps/dashboard/app/(tenant)/billing/page.tsx#L179-L180: replace “chain today” with audit-log terminology.apps/dashboard/app/(tenant)/billing/statement/page.tsx#L95-L95: update Line 128’s “chain entries” wording to “audit-log entries.”
📍 Affects 2 files
apps/dashboard/app/(tenant)/billing/page.tsx#L179-L180(this comment)apps/dashboard/app/(tenant)/billing/statement/page.tsx#L95-L95
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/dashboard/app/`(tenant)/billing/page.tsx around lines 179 - 180, Replace
“chain today” with consistent audit-log terminology in the billing page text,
and update “chain entries” to “audit-log entries” in the billing statement text.
Apply the terminology changes in both specified billing files while preserving
the surrounding UI content.
Comment on lines
157
to
162
| Point any OpenAI- or Anthropic-compatible agent at Ainfera, set{" "} | ||
| <span style={styles.inlineMono}>model="ainfera-inference"</span>, and | ||
| every call routes to the model most likely to finish the task — neutral | ||
| across providers, signed on chain. No model-pinning, no ten-vendor key | ||
| across providers, signed on the audit log. No model-pinning, no ten-vendor key | ||
| sprawl. | ||
| </p> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Complete the terminology migration across affected surfaces.
The changed strings introduce “audit log,” but related rendered and documented copy still uses “audit chain,” “AuditChain,” or “on chain.” Choose the approved terminology and apply it consistently at each site:
apps/marketing/app/agents/page.tsx#L157-L162: update the remaining “public audit chain” and “signed on chain” body copy.apps/marketing/app/namo/page.tsx#L14-L14: alignapps/marketing/content/agents.tsNamo content with the new metadata wording.docs/handover/2026-07-04-entity-boundary-proposal.md#L17-L17: update the proposal’s remaining “public audit chain” references.
📍 Affects 3 files
apps/marketing/app/agents/page.tsx#L157-L162(this comment)apps/marketing/app/namo/page.tsx#L14-L14docs/handover/2026-07-04-entity-boundary-proposal.md#L17-L17
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/marketing/app/agents/page.tsx` around lines 157 - 162, Complete the
terminology migration by replacing remaining “public audit chain,” “AuditChain,”
and “on chain” references with the approved “audit log” terminology. Update the
affected copy in apps/marketing/app/agents/page.tsx lines 157-162, align the
Namo metadata wording in apps/marketing/app/namo/page.tsx line 14 and
apps/marketing/content/agents.ts, and update the remaining “public audit chain”
references in docs/handover/2026-07-04-entity-boundary-proposal.md line 17.
|
|
||
| <section id="chain" style={sectionStyle}> | ||
| <div style={h2Meta}>02 · what goes on chain</div> | ||
| <div style={h2Meta}>02 · what goes on the audit log</div> |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Complete the terminology migration within each affected document.
The renamed strings are correct individually, but adjacent copy still uses the old “chain/on-chain” terminology. Align every related heading, metadata field, and neighboring description with the canonical audit-log language.
apps/marketing/app/privacy/page.tsx#L278-L278: replace the section’s remaining “chain” references with the chosen audit-log terminology.apps/marketing/app/terms/page.tsx#L8-L8: align the Open Graph description and related body copy with “audit log.”docs/AINFERA-WEB-CONTENT-PROPOSAL.md#L35-L36: update the adjacent Audit/proof row so the table does not mix “audit-log” and “on-chain” wording.
📍 Affects 3 files
apps/marketing/app/privacy/page.tsx#L278-L278(this comment)apps/marketing/app/terms/page.tsx#L8-L8docs/AINFERA-WEB-CONTENT-PROPOSAL.md#L35-L36
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/marketing/app/privacy/page.tsx` at line 278, Complete the terminology
migration across all affected content: in apps/marketing/app/privacy/page.tsx
lines 278-278, update the section heading’s remaining “chain” wording to the
canonical audit-log terminology; in apps/marketing/app/terms/page.tsx lines 8-8,
align the Open Graph description and related body copy with “audit log”; and in
docs/AINFERA-WEB-CONTENT-PROPOSAL.md lines 35-36, update the adjacent
Audit/proof row so it consistently uses audit-log language instead of mixing
“on-chain” terminology.
| <div> | ||
| <h2 style={styles.stepH2}> | ||
| Verify the call landed on chain. | ||
| Verify the call landed on the audit log. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Complete the terminology pass across adjacent user-facing labels.
The updated labels now mix “audit log”/“event” terminology with nearby “chain”/“block” wording, which makes the public copy inconsistent.
apps/marketing/app/quickstart/page.tsx#L659-L659: update or clearly identify the remaining block/chain labels in the verification example.apps/marketing/app/routing/page.tsx#L179-L184: update the proof heading, description, and block-height wording consistently.apps/marketing/components/site/SiteNav.tsx#L110-L110: align the visibleblocklabel with the new ARIA label.
📍 Affects 3 files
apps/marketing/app/quickstart/page.tsx#L659-L659(this comment)apps/marketing/app/routing/page.tsx#L179-L184apps/marketing/components/site/SiteNav.tsx#L110-L110
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/marketing/app/quickstart/page.tsx` at line 659, Complete the terminology
pass across all three sites: in apps/marketing/app/quickstart/page.tsx lines
659-659, revise the verification example’s remaining block/chain wording to use
consistent audit-log/event terminology; in apps/marketing/app/routing/page.tsx
lines 179-184, update the proof heading, description, and block-height label
consistently; and in apps/marketing/components/site/SiteNav.tsx lines 110-110,
change the visible block label to match its updated ARIA label.
| </div> | ||
| <pre> | ||
| {`# the public chain is keyless | ||
| {`# the audit log is keyless |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Complete the terminology migration in the affected marketing sections.
The changed strings introduce “audit log” wording while the same sections still expose old chain/block terminology, producing inconsistent public copy.
apps/marketing/components/site/ProofSection.tsx#L44-L44: update the surrounding “public chain” copy and the snippet’s “block height” wording.apps/marketing/components/site/LandingLiveRoute.tsx#L24-L24: ensure the points section does not sit beside stale “public audit chain” copy.apps/marketing/components/site/LandingLiveRoute.tsx#L39-L39: update the adjacent live-routing paragraph so it uses the same audit-log terminology.
📍 Affects 2 files
apps/marketing/components/site/ProofSection.tsx#L44-L44(this comment)apps/marketing/components/site/LandingLiveRoute.tsx#L24-L24apps/marketing/components/site/LandingLiveRoute.tsx#L39-L39
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/marketing/components/site/ProofSection.tsx` at line 44, Complete the
terminology migration across the affected marketing copy: in
apps/marketing/components/site/ProofSection.tsx:44, update the surrounding
“public chain” wording and the snippet’s “block height” terminology; in
apps/marketing/components/site/LandingLiveRoute.tsx:24 and :39, replace stale
“public audit chain” and live-routing terminology with consistent audit-log
wording.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RED-3: Audit-Language Pass (Linear Issue 3)
Replace all blockchain/on-chain/immutable language with honest Ed25519-signed append-only audit log terminology.
Changes (43 files, +86/-86)
on chain/on-chain→on the audit log/logged/signedblockchain→Ed25519-signed append-only audit logBlock #N/block #N→Event #N/event #Nimmutable→append-onlyBlock→Audit EventVerified clean
Post-replace grep (case-insensitive) across
apps/,docs/,scripts/,design/:on chain(two words) — zero hitson-chain— zero hits (only claim-registry.yml pattern definitions)blockchain— zero hits (only claim-registry.yml pattern definitions)block #/Block #— zero hitscannot rewrite— zero hitsimmutable— onlysw.js(HTTP cache semantics, correct) andTemplateEditor.tsx:148(standard English, correct)Not changed (correct English, kept)
sw.js— "immutable build assets" = HTTP cache headersTemplateEditor.tsx:148— "System templates are immutable" = standard Englishclaim-registry.ymlpattern definitions — these are the rules that detect violations, not violations themselvesNotes
Note
Low Risk
Copy-only terminology updates across UI, marketing, and docs with no behavioral or security logic changes.
Overview
RED-3 renames user-facing and internal copy so the product is described as an Ed25519-signed append-only audit log, not a blockchain or “on chain” system. There are no API, routing, or data-model changes—only strings, comments, and docs.
Across the dashboard and marketing apps, phrases like “on chain”, “signed on chain”, and “public chain” become “on the audit log” (or equivalent) on agents, routing, billing, keys, evals, get-started, privacy/terms, and shared site chrome (footer, nav, live feeds, curl verify snippets).
Audit detail UI shifts from block framing to event framing: page title Audit Event, headings/crumbs Event #N, timeline copy signed → event #N, and verify labels verify this event. Routes like
/audit/block/[seq]are unchanged; only labels and metadata move.Docs and tooling (
DESIGN_CANON.md, launch/content proposals, claim checks, marketing verify script) use the same vocabulary so canon, lint, and previews stay aligned with the new language.Reviewed by Cursor Bugbot for commit f1e7d09. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
UI and Terminology
Documentation