尚未偵測到更新。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.