尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证4orm Intelligence 支持消费者在重大金融决策中的需求。4orm 将客户共享的信息连接到企业的合规工具,实时提供可审计记录,无需事后重建以证明适合性。
AI 翻译
4orm Intelligence supports consumers through their major financial decisions. 4orm connects what information the client shares into the business's compliance tools, providing the auditable record in real time, without having to reconstruct it later to prove suitability.
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
Static site. No framework, no build step, no package.json.
The repository must stay private. This file, check.sh and the .banned-*
lists do not ship (see .vercelignore), because a note describing what the site
must not say is itself a description of what the site must not say.
4ormfinance.com carries the company, the vision and the sales story.
This site carries the screens.
It shows what the platform produces. It does not describe how anything is
produced. Patent applications are pending, so that boundary is not a style
preference, it is the point of the site.查看完整 README ↗Static site. No framework, no build step, no package.json.
The repository must stay private. This file, check.sh and the .banned-*
lists do not ship (see .vercelignore), because a note describing what the site
must not say is itself a description of what the site must not say.
4ormfinance.com carries the company, the vision and the sales story. This site carries the screens.
It shows what the platform produces. It does not describe how anything is produced. Patent applications are pending, so that boundary is not a style preference, it is the point of the site.
If you are about to add a sentence and you are unsure which side of the line it sits on, the test is: would a competent engineer be able to build something closer to ours after reading it? If yes, it does not go on a public page. It goes in a walkthrough, under a written agreement.
Safe to publish: the five screen names and the question each answers, an illustrative dashboard clearly labelled as a drawing, public law and its dates and penalties, outcome-level statements about what comes out, and the things we refuse to build.
Never publish: timings, sequences, anything about what runs without a person present, how records are kept or proved, how one platform serves more than one regulator, anything about feeds or storage, pricing, financials, team, or the name of any supplier.
| File | Route | data-page |
|---|---|---|
index.html | / | home |
the-duty.html | /the-duty | the-duty |
platform.html | /platform | platform |
inside-the-platform.html | /inside-the-platform | screens |
contact.html | /contact | contact |
404.html | not found | 404 |
assets/styles.css - the design system. Tokens carried forward unchanged.assets/chrome.js - injects the legend strip, nav, closing CTA, family block
and footer into empty mount divs, and drives the screen switcher on
/inside-the-platform. All config is in the CONFIG block at the top.assets/favicon.svg - navy tile, white 4, gold dot.The nav renders a typographic wordmark, so nothing is broken today.
To use the real mark: drop a transparent PNG at assets/logo.png and set
USE_LOGO = true in chrome.js. The nav sizes it at 120px tall on desktop and
steps down at 1240px and 1080px. If the source has a solid background baked in:
convert logo-input.png -fuzz 12% -transparent "#000000" assets/logo.png
python3 -m http.server 8080
cleanUrls is a Vercel behaviour, so locally you need the .html on the end.
Vercel, static. vercel.json sets cleanUrls: true, so /the-duty serves
the-duty.html. Push to main and it deploys.
Push from Cursor's Source Control UI, not from a terminal. The in-editor agent terminal cannot authenticate to GitHub for this account.
After a large content change, run "Redeploy without build cache" from Vercel's Deployments tab if the apex URL serves stale HTML.
./check.sh
Six checks: three typographic, three disclosure. All must pass. Adding a term to
a .banned-* list is routine. Removing one is a decision, so say why in the
commit message.