Negosyo Life — Phase 11 install and use

Version 0.11.0 · 23 October 2026

1. What this release builds

This cumulative package keeps the demo5 (opus v5.1) interface and all earlier phases. It adds six owner-operated business cases across three playable expansion tiers, separate unit books and monthly results, server-owned learning XP, a wholesale warehouse upgrade, safe closure and a launch-readiness desk.

The six cases are Neighborhood reseller, Food preorder kitchen, Laundry service, Print and layout studio, Small wholesale distributor and Creative agency. They teach different cash cycles: stock, spoilage, deposits, delivery revenue and delayed collection. The new units belong to your original company and use separately allocated company cash. They are not new personal assets, Phase 6 trade listings or shared-company entities.

This is still a fictional learning game for a small invited-adult pilot, capped at 25 careers. It is not real business registration, employment, banking, investment, property ownership or payment. The new cases use owner operation and authored outside fulfillment, without a second employee/payroll engine. Earlier employee/payroll lessons remain at their existing desk. Real site/activity-specific permissions and tax reporting need qualified review; the game does not submit anything to government.

Free authored mode needs only your own Cloudflare Pages and Supabase projects. No paid AI, live data feed or media bucket is required. Optional DeepSeek remains separately configured and off by default on a fresh install. Nothing was deployed or billed by this delivery.

2. Upgrade from Phase 10

1. Make a consistent database backup and Practice export. Retain the old deployment, public config and migration record.
2. Extract Phase 11 into a new folder. Copy your existing Supabase public values into site/config.js. Preserve your optional AI endpoint and its exact permitted Worker origin in site/_headers if you already use it. Never put secrets in either file.
3. Run supabase/018_catalog_and_launch.sql once after 016 in your own Supabase SQL Editor. Do not rerun successful old scripts or reset careers. This migration is transactional and intentionally not repeatable after success.
4. Keep existing jobs. Optional 019_optional_venture_worker.sql adds half-hour processing at minutes 08 and 38 after Cron is enabled. The original chronological shop worker also gains the venture hook; player reads catch up due work as well. Do not duplicate jobs.
5. Assign your verified operator Auth UUID using the commented template in LAUNCH_OPERATOR_SETUP.sql. The launch role is separate from social moderators, trade reviewers and trend reviewers.
6. Deploy the complete edited site folder to your existing Pages project. For ZIP upload, rebuild with python3 scripts/package_release.py after editing configuration, then upload Negosyo_Life_Phase_11_Cloudflare_Upload.zip.
7. Existing careers continue. New ordinary careers are blocked until all seven current-release hosted checks are recorded within the last seven days, in addition to the inherited admission cap/switch and maintenance gate. Existing admission settings are preserved; they do not bypass the new readiness check. Verified launch operators can start test careers within the cap for acceptance.
8. The new catalog starts disabled. Enable it only on staging for acceptance, complete PHASE11_ACCEPTANCE.md, then enable the small checked pilot as described below. No readiness checks are pre-filled in a real installation.

018 adds no grant or new business automatically. It preserves earlier obligations and wraps selected commitment RPCs with a maintenance gate, retaining original signatures, economics, permissions and receipt handling. It adds a chronological venture hook before company spending capacity is returned. Uncovered recorded venture bills/advances reduce original-company spendable cash; internal recovery allocations still protect the existing payroll/refund reserve.

From older releases, apply only missing mandatory scripts in order: 004 → 005 → 006 → 008 → 010 → 012 → 014 → 016 → 018. Keep optional schedules separate.

3. Fresh installation and first operator

Use projects in your own accounts. Run mandatory files once in this order:

Optional Cron installers: 003, 007, 009, 011, 013, 015, 017 and 019, each once after its prerequisite. 017 creates free authored drafts only. Preserve earlier feature/operator settings separately; archived Phase 3–10 guides and their operator scripts remain in the full package.

Edit public configuration only:

window.NEGOSYO_CONFIG = {
  supabaseUrl: 'https://YOUR_PROJECT_REF.supabase.co',
  supabasePublishableKey: 'sb_publishable_YOUR_PUBLIC_KEY',
  trendAiEndpoint: ''
};

Use the actual project HTTPS URL and publishable key. Never include a database password, secret/service-role key or DeepSeek key. For optional paid inference, retain the separate Worker instructions in PHASE10_AI_SETUP.md; no new AI service is required here.

Use Cloudflare Pages Direct Upload with the contents of site, putting index.html at the upload root, or use the rebuilt public ZIP. The supplied public ZIP has blank cloud settings. Do not upload the full source ZIP, SQL, tests, operator files or optional_ai. No npm build is needed for the supplied static site.

Set Supabase Auth Site URL and exact /index.html callback to your production HTTPS origin. Test confirmation, sign-in, recovery and sign-out. Create/confirm your operator Auth account first; then verify its exact Auth UUID in your project. As project owner, assign it to negosyo_private.launch_operators using the commented setup template. This role can be assigned before a Live career exists, so it can bootstrap acceptance.

Sign in with that account and open Launch readiness. Start its Live career for testing if needed. It must still fit the inherited admission cap, enabled admission and maintenance-off state. Never assign arbitrary players as operators merely to bypass readiness. A launch operator can inspect readiness and perform launch actions without an existing career.

For local viewing, use START_WINDOWS.bat with Python 3, or python3 -m http.server 8000 --directory site, then open http://localhost:8000. Practice remains separate and accelerated. Live catalog, XP, money and operator records require configured Supabase; offline screens do not fabricate them. For development use Node.js 22+, npm ci, then npm test.

4. Learn and unlock businesses

Open Business catalog or Learning journey. Complete the original paperwork trail through the BIR/invoice learning step and all three expansion lessons: margin, cash/collections and continuing obligations. They award 20 XP each, once, for 60 foundation XP.

Equipment also depreciates by 0.1% of its opening equipment cost per completed ownership day, until its book basis is zero. These are authored teaching amounts, not market prices, legal tax depreciation or a forecast. Upkeep continues at zero equipment basis and while paused. A warehouse upgrade has its own additional cost below.

A profitable business with at least one collected operating receipt can earn 40 mastery XP once per type. Enter its exact cumulative operating profit and correctly distinguish profit from cash. Repeated answers, opening/closing, allocations, clearance proceeds and clicks never generate repeat XP. Higher tiers require experience and capital, not spending real money.

You may have at most three operating/paused units, one per business type, and 30 lifetime unit records in this pilot. A paused unit still occupies a slot and has costs. You can focus on one business or move between models. No grant is added for unlocking a tier. Tiers 1–3 are playable; tiers 4–10 remain future content, and there is no ending or mandatory streak.

5. Operating models and location fit

Four authored locations are available: home, market, office and industrial. Each model lists its good-fit locations. Poor fit halves goods demand (rounded down, minimum one) or reduces the service fee to 75%. Costs do not shrink with the fee. This is a simplified location lesson, not live NCR property data, an actual tenancy or ownership of a parcel. Authored overhead includes the modeled premises/support costs; no second original-store lease is created.

Reseller: small batch 30 units × ₱60, large batch 60 × ₱60; arrival after 12 hours. Price ₱100/unit; good-fit daily demand six. A supplier prepayment is work in progress, then inventory at arrival. Recognize cost only as units sell or are cleared/written off.

Food: small batch ten × ₱50, large batch twenty × ₱50; arrival after six hours. Price ₱90/unit; good-fit daily demand ten. Unsold stock expires 24 hours after arrival and its remaining basis becomes expense. A large batch can lose money despite visible gross sales. Expiry wins a tie with the next sales slot. All leftovers must be sold, expired or cleared before another batch.

Wholesale: small batch 60 × ₱60; large batch 120 × ₱60 requires the upgrade. Arrival after 24 hours; good-fit daily batch sales thirty × ₱80. Revenue becomes a receivable, collected 48 hours after each sale. Delivery does not itself create immediate sales: goods use daily customer slots anchored to founding. Arriving just after a slot may delay the first sale to the following slot. The first cash collection can therefore take several real days.

Laundry: fee ₱1,200, direct fulfillment ₱600, 50% customer advance, delivery after 24 hours; remaining payment arrives on delivery. Printing: fee ₱1,500, direct cost ₱700, 50% advance, 12-hour delivery plus 24-hour collection. Agency: fee ₱3,000, direct cost ₱1,500, 25% advance, 48-hour delivery plus 48-hour collection. These are authored deterministic clients, not actual buyers or a modeled default/credit-scoring system.

Service fees adjust for location fit. An advance is a liability until delivery; delivery releases that liability and recognizes revenue. An unpaid balance is a receivable, not spendable cash. Collecting it later moves the asset into cash without a second sale. The direct cost is prepaid work in progress until delivery. Protect advances and bills; fund fulfillment from safe working capital rather than treating a deposit as free profit.

There is one pending supply or service job per unit; delivered receivables can remain outstanding. Up to 30 recent job/event records appear per unit. A small/large batch is selected at fixed server terms; the browser cannot choose its price, cost, delivery clock or outcome. Phase 10 trend effects remain limited to the original starter retailer, not these new models.

6. Books, cash recovery and closing

HQ, My businesses and Books link to the Venture desk. It shows cumulative expansion gross sales, direct costs, operating expenses and operating result, including closed units. Each unit has its own cash, safe available amount, inventory, work in progress, receivables, customer advances, unpaid overhead, equipment basis, journal and latest twelve monthly results. Monthly results use Manila calendar dates and clearly label the current partial month.

Gross sales − direct costs − operating expenses = operating profit/loss. The new report is before any separately modeled tax; it is not a real tax return. The original-store, brand, shared-company and personal reports remain separate. Expansion totals are a segment, not a consolidated company statement. Funding and collecting old receivables are never new sales.

Opening allocates equipment and working cash from original-company funds. It does not spend personal funds or create a new legal entity. Add allocation only within the original payroll/refund reserve. Return safely available unit cash to the original company while protecting that unit's recorded bills, advances and ₱100 reserve. It is an internal capital movement, not personal income. The existing Owner withdrawal desk separately checks company obligations before personal spending.

Recorded venture bills/advances not covered by allocated venture cash reduce original-company spendable cash. Internal recovery allocation is permitted from original cash after the prior payroll/refund/₱2,000 reserve, so a unit can be funded to pay its bill rather than deadlocking against the bill reserve. Daily venture processing also runs through the original chronological core before original-company spending is checked.

Paying recorded overhead clears a liability without expensing it twice. Pause stops new unit commitments and automatic goods sales, while daily overhead/depreciation, existing fulfillment, receivable collection and food expiry continue. Resume needs the catalog and maintenance gates to allow it.

Wholesale can buy ₱2,000 of warehouse equipment to increase capacity from sixty to 120 units. This adds ₱20 daily overhead and ₱2 daily depreciation. It is an equipment/capacity record, not property title, a rentable building or a new employee. It can be purchased once per unit with safe cash.

Clear inventory sells to an NPC for 50% of remaining inventory basis and recognizes the other half as loss. It creates no operating-sales/mastery receipt. Safe closure requires no stock, pending work, uncollected receivables, customer advances or unpaid bills. Equipment is then disposed of at 50% of remaining basis, the loss is recorded, and remaining unit cash returns to the original company. Closed records remain; their losses do not vanish. These units are not automatically available for player-to-player trading or franchising.

7. Timing, workers and safe retries

Check once or twice daily. No button advances time. Goods have one customer batch per completed 24-hour slot, bounded by inventory and fit. Costs accrue after each complete 24-hour ownership period. Service/supply/collection commitments use their actual due instants; the hourly core processes due work at a subsequent eligible whole hour, while unit reads/optional 019 can process up to their current server time. Timing may include the scheduled-worker interval.

The inherited core catches up at most 168 chronological hours per call. Each unit settlement invocation processes at most forty due events in due-time order; the hourly hook may invoke it for each recovered hour. Unit state adds a final bounded catch-up. A catch-up banner means refresh again before a new command. No backlog is silently discarded. The pilot caps owners and unit counts; it is not sized for unlimited traffic.

An uncertain venture command keeps its original UUID in the account's session receipt. Use Check / retry venture receipt. Replay returns the existing result; altered content fails. Stale unit revisions require a fresh review. Changing accounts clears displayed private state and dialogs, and late responses cannot populate the new account.

8. Launch readiness and maintenance

Open Launch readiness with a verified launch operator. It displays sanitized public state and private aggregate diagnostics: career count, backlog over 168 hours, unbalanced journal count, unit book/inventory mismatch count, trend queue/pending AI counts and database bytes. These are limited signals, not a security audit or proof of a restore.

Complete the actual hosted checks in PHASE11_ACCEPTANCE.md: auth, permissions, concurrency, schedules, restore, mobile and quotas. Record each only after successful staging verification. They are manual operator attestations for release 0.11.0. Local automated tests do not fill them. All seven must be current within seven days for new ordinary careers; expiry blocks new ordinary starts without deleting or freezing existing careers. Operators retain the limited bootstrap exception within the original cap and admission/maintenance gates.

Use the desk to close career admission at any time. Reopening requires the seven recent checks, maintenance off and a cap from one to 25. The server still enforces the cap atomically. Reducing it does not delete careers. This controls game careers, not Supabase Auth signup; configure your Auth invitation/signup settings separately for your intended pilot.

Use Maintenance to pause selected new commitments with a plain public notice. The server applies the gate even if the frontend is old or modified. Successful earlier UUIDs may still replay their receipts, but changed replays cannot mutate anything. Reads may settle time commitments: maintenance is not an account freeze.

The underlying earlier feature switches still apply. An allowed recovery category does not override ownership, reserves, dispute review or another feature's guard. The AI gate blocks new reservations; a previously reserved provider call may finish, so remove/rotate the optional Worker secret or stop that Worker for an external-call emergency. No automatic paid call is added.

For staged catalog acceptance, the SQL owner may set negosyo_private.venture_settings.enabled=true. After actual acceptance, use the same deliberate operator setting for the small pilot. Set it false to block new expansion; committed work and recovery continue. LAUNCH_OPERATOR_SETUP.sql supplies commented templates. No file silently enables the catalog or opens a public launch.

9. Deployment, backups and operating the pilot

Read PHASE11_RUNBOOK.md before admitting players. Retain the previous frontend and a consistent full database backup. Supabase's official guidance recommends regular logical exports and off-site copies for free projects; do not assume this ZIP gives you managed backups or point-in-time recovery. Use the linked official export/restore procedure and actually test a restore into a disposable project before recording that readiness item.

Preserve app schema/data, private schema/functions/receipts, Auth user identity mappings and project configuration; provider keys/secrets and external settings require separate secure handling. A restored database does not automatically restore every external service or any Storage object bytes. Do not put backup credentials or private exports in Pages, public ZIPs or this chat.

Monitor provider dashboards for real quotas, errors, email, CPU/requests and database growth. The displayed database byte count is only one signal. Keep the 25-career/three-unit limits and turn off paid AI for a free-only pilot. No photo/video uploads or external feed is required. Retained journals/receipts are finite-capacity data: plan a reviewed archive/migration strategy as the endless game grows, rather than deleting obligations to save space.

No credentials or deployment were provided, so production Auth/Cron/network, simultaneous hosted clients, real recovery/restore, load and narrow-device acceptance remain operator work. The package includes local regression evidence and a hosted checklist, not a claim of completed production certification.

10. What remains after Phase 11

The eleven planned builds now have their scoped implementations. This does not make the full original tycoon vision complete. Tiers 4–10, deeper business-specific staffing, player-to-player franchises, shared-company brands, real supplier logistics, sponsored placements, a startup/IPO system and an autonomous AI economy remain future content.

There is no ending screen: expand content and balance the pilot over time. For launch, complete hosted acceptance first, start with a small invited group, inspect real usage and books, then decide on further releases. Optional monetization/sponsorship should be explicitly designed and disclosed before adding it; no ad network or tracker is silently installed.

What comes next

The scoped eleven builds are packaged. Complete actual hosted acceptance before the invited pilot. Further releases can deepen tiers 4–10, staffing, player franchises and carefully disclosed sponsorship.