Every number, and the rule that produced it.

Stated position

Give the pull list nameplate amps when you have them. If amps are missing, declared VA can be converted to current. Watts are the last fallback and are visibly labeled an estimate because AC equipment can draw more current than real watts alone imply.

Needs

Per-line quantity · Nameplate amps, VA, or watts · Supply voltage for VA/watt conversions

Where you meet it

Vendor Pack · Pull list & power · Lighting role sheet

My position / screening policy

Atmosphere's input-precedence policy uses manufacturer/nameplate current first, then apparent power divided by voltage, and only then real watts divided by voltage as an estimate. The electrical relationships are standard; choosing this precedence and aggregating them as a planning screen is a product policy.

What it does not claim

Not an electrical design calculation. It does not model phase, power factor beyond a declared VA value, inrush, harmonics, non-sinusoidal loads, phase balance, conductor ampacity, voltage drop, connector ratings or protective-device coordination. Manufacturer data and the responsible electrical professional take precedence.

src/lib/vendor-pack/equipment.ts

Stated position

The pack adds 25% headroom to its current estimate before comparing it with declared venue capacity. That is a conservative house screen, not a statement that every event load is legally a continuous load.

Needs

Amps from POWER-AMPS-01

Where you meet it

Vendor Pack · Pull list & power

My position / screening policy

My conservative planning policy: apply 25% headroom to the whole working current estimate. NEC 210.19(A) / 210.20(A) use 125% sizing for continuous loads; the NEC definition is tied to maximum current expected for 3 hours or more and includes exceptions. Atmosphere OS deliberately applies the allowance more broadly as an early planning screen. It does not claim IEC equivalence.

What it does not claim

The result is not a branch-circuit design, code determination or permission to load a circuit to the displayed value. Continuous/noncontinuous classification, 100%-rated equipment, local code and the actual protective device are outside this model.

src/lib/vendor-pack/equipment.ts

Stated position

A quick count for whether the declared supply deserves a closer look. It does not assign loads to circuits or prove those circuits can serve the equipment.

Needs

Derated amps · Amps per circuit at the venue

Where you meet it

Vendor Pack · Pull list & power

My position / screening policy

My planning screen divides the headroom-adjusted aggregate current by the venue-declared amps per circuit and rounds up. The arithmetic is deterministic; treating aggregate amps this way is not a circuit design.

What it does not claim

Does not account for voltage, phase, phase balance, shared neutrals, connector type, load diversity, inrush, branch-circuit topology, existing house loads or local electrical requirements. The responsible electrical professional designs and approves distribution.

src/lib/vendor-pack/equipment.ts

Stated position

A negative result is a red flag. A positive result is not electrical approval, because real circuits, phases and existing loads are not one interchangeable bucket.

Needs

Declared circuits · Amps per circuit · Derated amps

Where you meet it

Vendor Pack · Pull list & power · Vendor Pack · Still undeclared

My position / screening policy

My aggregate screen multiplies the declared number of circuits by declared amps per circuit, then subtracts the headroom-adjusted planning current. The subtraction is exact; treating those circuit ratings as one interchangeable pool is only a first-pass product screen.

What it does not claim

Does not prove that individual circuits, phases, connectors, feeders or conductors can carry the proposed loads. It also does not establish voltage compatibility or available capacity after house loads.

src/lib/vendor-pack/equipment.ts

Stated position

Missing electrical data stays missing. Assumed watts can help size a planning scenario, but they remain outside the declared-current floor and are printed as assumptions until replaced by real equipment data.

Needs

Which lines declare A / VA / W · Which watt values are explicitly assumed

Where you meet it

Vendor Pack · Pull list & power · Every role sheet

My position / screening policy

My evidence policy: the application may carry an explicitly labeled planning assumption, but it never invents an unlabelled 'typical' draw for a line with no electrical declaration.

What it does not claim

The working total is still short by every line that declares no amps, VA or watts. An assumed wattage also remains weaker evidence than manufacturer/nameplate current or VA.

src/lib/vendor-pack/equipment.ts

Computed

How wide the pool of light is by the time it reaches the table.

Needs

Throw distance · Beam angle

Where you meet it

Vendor Pack · derived lighting · Room elevation

Basis

Trigonometry of a cone.

src/lib/spatial/room.ts

Stated position

Use this to catch the common mistake of quoting a bright pin-spot center as though the whole table receives that illuminance. It is a comparison model, not a photometric calculation.

Needs

Fixture lumens · Beam pool area · Table area · Candle count

Where you meet it

Vendor Pack · derived lighting · Room elevation

My position / screening policy

My photometric planning approximation: fixture lumens are spread over the larger of beam-pool or table area, with a small candle-light allowance. The center-vs-average distinction is physically real; the simplified distribution model and candle term are mine.

What it does not claim

It ignores candela distribution, beam falloff, fixture efficiency, tilt, overlap, reflectance, spectrum, obstructions and measured room contribution. Verify lighting with fixture photometry / manufacturer data and the lighting professional.

src/lib/spatial/room.ts

Stated position

A 1.8 m round seats eight, not ten. Ten is the banqueting squeeze, and you can declare it - but you have to declare it.

Needs

Table shape · Table size

Where you meet it

Every module that counts tables

My position / screening policy

My position: 0.65 m is the elbow-to-elbow width one diner needs to eat without apologizing. Below about 0.60 m people knock each other's glasses. Hotel banqueting will plan to 0.55 m and the room feels it all night.

src/lib/spatial/seating.ts

Computed

Linen, covers, centerpieces, pin spots, stem counts and the service pass all count the same tables. They used to disagree.

Needs

Guest count · Declared table count or seat count · Table geometry

Where you meet it

Floral · Arc Studio · Vendor Pack · Room elevation

Basis

Ceiling, because a fractional table does not exist. Precedence, because a declared number always beats a derived one.

src/lib/spatial/seating.ts

Stated position

The displayed band is a quick sightline screen for low-versus-elevated centerpieces, not a universal human dimension. Test the actual vessel and arrangement from occupied chairs before production.

Needs

Table height · Seated eye height · Standing eye height

Where you meet it

Floral brief · Room elevation · Moodboard proportions

My position / screening policy

A house sightline screen built from adult eye-height anthropometry plus explicit 60 mm / 50 mm planning margins. The anthropometric inputs are population summaries; the margins and the resulting dead-zone recommendation are Atmosphere OS planning positions.

What it does not claim

Eye height varies by person, chair, posture and mobility device. Vessel width, stem density and table geometry also affect visibility. The field test in the real seating layout wins.

src/lib/spatial/room.ts

Computed

A planning estimate of queue wait from arrival rate, service rate and number of servers. It is useful for comparing staffing scenarios; it does not predict the exact line at a particular minute.

Needs

Arrival rate · Service rate · Number of servers

Where you meet it

Guest Journey · capacity

Basis

The Sakasegawa / Allen-Cunneen multi-server waiting-time approximation with arrival and service variability factors fixed to the exponential case. It is a published approximation, not exact Erlang-C M/M/c queueing arithmetic.

What it does not claim

Assumes stationary average rates and identical servers. Burst arrivals, batching, priority service, blocked stations, changing menus and correlated service times can move the real queue materially. At utilization >= 1 the steady-state estimate is refused and backlog is reported instead.

src/lib/gjp/capacity.ts

Stated position

The figure is a red-flag screen for whether décor, furniture or production may be consuming too much exit width. It is not the venue's legally required egress width.

Needs

Guest count

Where you meet it

Moodboard · proportions · Guest Journey

My position / screening policy

My cross-jurisdiction screening policy, informed by but not identical to building code. 2024 IBC 1005.3.2 uses 5.1 mm/person for non-stair egress components, with a 3.8 mm/person exception for qualifying sprinkler + emergency-voice conditions. England's Approved Document B Table 2.3 uses discrete minimum widths through 220 people and 5 mm/person only above 220, with exit-discounting rules. Atmosphere therefore uses 5 mm/person plus a 1.1 m floor only as an early conservative prompt.

What it does not claim

Never use this figure for occupancy approval, exit-count design or code sign-off. Jurisdiction, occupancy, sprinkler/voice provisions, stairs, exit count and distribution, door clear width, travel distance, accessibility, exit discounting and the authority having jurisdiction determine the real requirement.

src/lib/moodboard/tablescape.ts

Stated position

A forty-person dinner and a four-hundred-person gala do not take the same time to serve. This is why.

Needs

Guest count · Seats per table · Service style · Course count

Where you meet it

Arc Studio · act maths · Run sheet

My position / screening policy

My position: roughly 2.5 minutes of service per course per table, and one service team covers about three tables before the pass stops being one pass.

src/lib/arc/acts.ts

Computed

Which load-in tasks have no room to slip. If one of these runs late, doors run late.

Needs

Task durations · Declared dependencies · Phase order

Where you meet it

Vendor Pack · production schedule · Derived constraints

Basis

The critical path method, unmodified. Dependency ordering uses Kahn's algorithm, and a cycle is reported rather than silently dropped.

src/lib/vendor-pack/production.ts

Computed

You have this many minutes between the door being unlocked and the first guest arriving. Here is whether your build fits inside them.

Needs

Access time · Doors time · Critical path length

Where you meet it

Vendor Pack · production schedule

Basis

Clock arithmetic, with the shortfall quoted in minutes.

src/lib/vendor-pack/production.ts

Computed

A declared constraint can block a catalog stem and require any proposed substitute to clear the same recorded gates. The florist still verifies real cultivar, season, supply, mechanics and guest-specific sensitivities.

Needs

Season · Declared constraints · Water availability · Stem catalog

Where you meet it

Floral Direction · blocked stems

My position / screening policy

My deterministic gate over the attributes in the current stem catalog. There is no score: a stem either clears each declared constraint recorded for it or it does not. The result is only as current and specific as those catalog attributes.

What it does not claim

Catalog seasonality, scent, allergy and hardiness are planning attributes, not a medical or sourcing guarantee. Current wholesaler availability and the florist's professional judgment take precedence.

src/lib/floral/volume.ts

Stated position

Use the curve to compare where another dollar changes the plan most inside Atmosphere OS. Do not read the output as measured guest delight, market value or a promised return on spend.

Needs

Spend in a category · That category's fixed cost · Per-guest cost · Guest count

Where you meet it

Budget-to-Atmosphere · sensitivity · Decision brief

My position / screening policy

My saturating comparison model. It is intentionally shaped so marginal modeled effect falls as spend rises after a category floor. The curve is a decision aid, not an empirical law of event-design value.

What it does not claim

The fixed and per-guest figures are indicative planning bands for a mid-market metro, priced as of 2026. They are comparison controls, never quotes.

src/lib/budget/costModel.ts

Stated position

A repeatable way to expose trade-offs and shortfalls, not a claim that this is the objectively correct way to spend an event budget.

Needs

Total budget · Scenario weights · Category floors · Guest count

Where you meet it

Budget-to-Atmosphere · Decision brief

My position / screening policy

My deterministic envelope-allocation procedure: scenario weights set the first pass, category floors repair underfunded lines, and reserve receives rounding residual. The arithmetic is repeatable; the weights and floors are product positions.

src/lib/budget/evaluate.ts

Stated position

Where your project requires a vendor COI, the pack can flag whether the record you entered includes receipt, carrier, additional-insured status and an expiry that reaches the event date. It does not decide whether those terms are legally required.

Needs

Certificate records · Event date

Where you meet it

Vendor Pack · insurance · Vendor library alerts

My position / screening policy

My document-completeness checklist for a project that has already decided a COI is required. Requirements for certificates, limits, endorsements and additional-insured status come from the applicable contract, venue, insurer and jurisdiction; they are not universal across every vendor.

What it does not claim

This does not authenticate a certificate, verify active coverage, interpret policy language, determine required limits or endorsements, or give insurance/legal advice. Contract and venue requirements control.

src/lib/vendor-pack/paperwork.ts

Computed

CIEDE2000 reports perceptual color difference under its defined reference conditions. Lower values mean closer modeled colors; Atmosphere OS does not impose a universal 'indistinguishable' cutoff on a real event room.

Needs

Two colors · Illuminant

Where you meet it

Theme Atelier · palette · Floral palette read

Basis

CIEDE2000, the CIE standard color-difference formula. Implemented in full.

What it does not claim

Do not reuse the often-quoted 2.3 value as a CIEDE2000 just-noticeable threshold; that number is commonly associated with older CIELAB/CIE76 discussion. Perceptibility depends on viewing condition, adaptation, sample size, surround, observer and material. Physical samples under event light remain the acceptance test.

src/lib/color/index.ts

Computed

Use this ratio for digital guest-facing interfaces, PDFs or screen assets where WCAG text contrast applies. It is a useful warning for palette pairings, not a certification of a printed menu or sign.

Needs

Foreground color · Background color

Where you meet it

Theme Atelier · palette · Stationery notes

Basis

WCAG 2.2 contrast-ratio arithmetic for digital text: 4.5:1 for normal text at AA, 3:1 for qualifying large text at AA, and 7:1 for normal text at AAA (with the standard's stated exceptions).

What it does not claim

WCAG is a web/digital accessibility standard. Printing process, substrate, finish, ambient illumination, type size/weight and viewing distance need their own proofing. The ratio alone does not establish accessibility of a physical sign or stationery item.

src/lib/color/index.ts

Computed

Turns a chosen Kelvin value into an idealized blackbody chromaticity so the palette can be stress-tested under warmer or cooler light assumptions.

Needs

Chromaticity coordinates

Where you meet it

Theme Atelier · palette under light

Basis

Kim et al.'s polynomial approximation of the Planckian locus over the stated Kelvin range. The engine uses it to construct an idealized blackbody white point for simulation; it is not measuring a fixture's CCT from a spectrum or sensor reading.

What it does not claim

Real fixtures with the same nominal CCT can differ in Duv/tint and spectral power distribution, and therefore in color rendering. CRI/TM-30, metamerism, gels and fixture-specific spectra are outside this calculation.

src/lib/color/index.ts