Norulo Web

The Project capacity fix is published in production as of 2026-10-12. Deleting a project releases its project place; Billing, creation limits and all six languages share the current undeleted-project definition. Final integrated main passed 1,706 tests. See deployment verification for the exact source commits, Worker versions and read-only production checks.

The user has now confirmed ordinary expense recording works. The current release also fixes mobile profile spacing and narrow-screen project setup steps. Empty payment configuration supports Free use; paid checkout remains unavailable until real payments are configured. See production operations and the dated free-launch verification in the deployment notes for acceptance limits, safe logging and daily scheduling.

Current deployment: the Norulo frontend application has been published to Cloudflare for norulo.com and www.norulo.com. The full Python Server is published at api.norulo.com, with production D1/schema 12 verified. Direct and proxied health checks return 200; unauthenticated account reads return 401. The user reports successful GitHub login. Production email authentication is enabled with sender [email protected]; the user confirmed receiving the code and successfully signing in. Repository installation, account linking and ledger journeys remain unverified. AI quality verification passed with 36 valid direct-provider responses; local monthly Owner-quota checks also passed. Its Server-only key is bound in the cloud network configuration. Verified release B on 2026-10-11 at 06:38:08.477224 UTC enables AI and production recurring with all five activation flags 1 and one daily 10 16 * * * cron (Beijing 00:10 the next day). Checked-in flags retain safe 0 defaults. Recurring passed local native Worker/Durable Object verification and independent review. Exact source commits and versions are recorded as a dated release snapshot in the deployment notes. The published daily scheduler uses up to eight logical Owner lanes. LOCAL capacity profiles and the final 3,009-test Server regression run passed; official configuration GETs verified 300,000ms CPU and 9,000 subrequests. Release A's hourly configuration remains dated history. Release B is a verified snapshot, not a guarantee about subsequent HEADs or deployments. Real Worker/provider HTTPS and paid business journeys remain unverified. Preview publication is excluded. See deployment status for the exact version, CI result and public HTTP verification status. Records in docs/validation describe inherited source history and do not establish a Norulo release. See migration notes.

The verified public GitHub App slug is norulo (App). The supplied Norulo logo is installed in all icons and social cards. See brand assets for its original file, checksum and reproducible asset commands. Keep configured Cloudflare credentials in environment settings.

Norulo is a project expense ledger for developers and teams at norulo.com. Norulo Web is its browser client; the current product design describes the shared Web/Server contract. Members sign in with GitHub, create named projects, record project or shared expenses, manage categories, and review per-currency reports in the selected ledger. GitHub repository links are optional. API keys and platform subscription billing are separate from user-entered expenses.

Track project and shared expenses. Keep every cost in view.

The shared pool records costs used across projects once in the selected ledger; it does not allocate or copy them into individual projects. Each currency is totaled separately, without currency conversion. Expenses are entered by users, authenticated API clients or configured recurring rules; linking a repository does not import bills or move money.

The workspace/team and multi-repository implementation is included in the imported application. Current Norulo verification and publication are recorded in the migration and deployment notes; dated source acceptance records remain separate historical evidence.

Workspaces and projects

An existing owner's ledger becomes a workspace identified by that owner's ID; personal ownership remains an implicit Owner. The header picker switches between the personal ledger and ledgers joined by invitation. Protected views clear their data, drafts and one-time credentials when the workspace or access scope changes, abort obsolete reads and ignore late results.

Members supports invitation links, applications, original-inviter approval, role changes, removal and invitation revocation. Applicants sign in with their own account; access starts after approval. Owner manages Admins; Admin manages Editors and Viewers. Editors record expenses; Viewers can read reports and export CSV. Invitation creation and acceptance warn that membership shares all current and future ledger data. Membership does not grant GitHub access. Team usage pools the owner's ledger quotas, plan and model allowance; billing stays with the owner, and each member's personal ledger remains separate.

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗