# Authoring instructions

This repository publishes Luke Nathan Hayes's escape-room network business plan. This is ROUND ONE exploratory research. AI extends research and computation; the manuscript must not prescribe an operating agent suite or treat scenarios as founder choices.

Read content/plan.json, content/finance.json, content/sources.json and briefs/approval-register.md before changing the plan. The canonical manuscript is content/plan.json. The website and portable Markdown edition are generated from it. Keep the PDF and Word edition consistent with the same manuscript.

Use Australian English, AUD and metric units. Do not use em dashes in newly authored prose. Preserve original source files unchanged. The plan begins with the executive summary and its clear business proposition. Language analysis and whole-of-life learning belong in the middle of the business plan.

Luke retains the business decisions. Clearly separate source observations, worked assumptions and actual founder decisions. Do not imply a model, price, premises, room count, timeline, technology, operating structure, contractor role or financial assumption has been chosen. Label numerical scenarios as comparisons or worked illustrations. Retain source dates and distinguish advertised prices from requested quotations. No quotation date may be invented. Do not execute operating workflows, contact people, hire, spend, enter agreements or create schedules as part of authoring. Keep this framing in generated pages, briefs and downloads.

Rooms run without hints. Microphones and event records support reflection after play. Include destructive-language noticing, useful disagreement, vocabulary, teamwork and skill transfer. Staff address safety, access or technical failures directly.

Capacity is calculated from physical rooms, group sizes, session durations, reset times, staffed hours and demand. Never import the compute project's population-per-node calculation. Distinguish visitor spending, ticket sales, partner settlements, referral fees, installation income and local operating surplus.

Preserve the Strange But True Public Source Licence. Do not substitute an open-source or Creative Commons licence. Personal Auras and data belong to their people. C-Hour is non-monetary. Keep paid work, investment and voluntary contribution in separate records.

All new hero images must be unique to their page, with prompts and provenance in content/artwork.json. Keep the established navigation: All chapters, on-page section links, previous/next chapters and return-to-top control.

Recording is a core design feature with a clear opt-out, not an optional add-on or an equivalent unrecorded format. Opt-outs must work across all capture channels. Keep research dates short and do not repeat them in following prose. Prefer formulas and editable calculators to long worked calculations. The executive summary must contain sourced capacity, competitor prices and labelled throughput/turnover comparisons scaled across rooms and locations. Keep individual-venue observations separate from operator subtotals. Never invent installation task hours or imply published charge rates validate assumed hours.
