Groundsworth · Prototype v2.1 · Parking lot

Deferred by design

Good ideas we have deliberately removed, deferred, or left dormant — kept here so a short-term scope call never loses a long-term idea. Every card says where the idea lands when it returns, why it's parked, and what triggers re-entry.

← back to the site map

The convention

Two markings, one rule. A deferred capability that is still visible in the prototype carries the amber post-launch pill in place (Billing, the Listings option, the post-launch map layers). A capability that is removed entirely gets a card on this page instead. The rule: no good idea leaves the prototype without one or the other. When a future revision cuts something worth keeping, add its card here — name · where it lands · why parked · re-entry trigger · source.

Parked — removed from the prototype, idea kept

Tray "Compare" view parked

Side-by-side comparison of tray selections before attaching them to a job — a triage surface between Explorer results and the grid.

Lands: Explorer / Comps · Why parked: removed in v2.1 to avoid a fourth comp surface; the ranked finder + grid should carry this weight first · Re-entry: design partners find pre-attach triage insufficient with finder + grid alone · Source: gap analysis P10

Sales-based value surface (the heat-grid successor) parked

A $/acre contour layer on Explorer derived from the firm's Ring-1 verified sales — the defensible successor to the removed CAD-assessed heat grid (assessed values are a questionable basis for appraisal work; 1-d-1 ag-use divergence).

Lands: Explorer layer panel · Why parked: heat grid removed from Increment 2 and the TX launch set 2026-07-21 · Re-entry: recorded in the data-source layer — a new descriptor + bake stage, or the sales-based surface once Ring-1 density supports it · Source: data-source layer (widened 2026-07-21)

Assistant-turns usage meter parked

Per-firm assistant-usage visibility. Dropped from the tenant Billing panel because a visible turn meter reads as metered-billing-in-waiting beside "assistant included on every seat — never an upsell." The durable usage ledger still records it ops-side.

Lands: Billing & usage (post-launch) or an ops console · Why parked: optics vs the committed never-an-upsell posture · Re-entry: billing surfaces get designed post-launch · Source: gap analysis C4 · delivery & ops (usage ledger)

Duplicate-match hints inside the Database view parked

The removed inline candidate row (C6) had a kernel worth keeping: surfacing "matches your #1042 — merge or skip" where the appraiser is already looking, not only in the candidate lane.

Lands: Comps · Database (as a hint ribbon, never a row) · Why parked: candidates must not appear inside Ring 1; the row broke the wall · Re-entry: Wave-3 Comps/import design · Source: gap analysis C6

Post-launch — visible in the prototype, amber-pilled

Listed here for the record; each is marked in place.

Billing & usage panel post-launch

Seats, pack line-items, usage tiles — good IA, out of launch scope by the domain-model ruling. The committed hook is the durable usage ledger.

Marked in: Settings · Re-entry: pricing point-in-band ruling + first billing increment

"Listings" as an evidence kind post-launch

v1 evidence kinds are ruled: sales · leases · cap-rate observations. List/ask prices remain candidate-lane metadata meanwhile.

Marked in: Explorer kind selector (disabled option) · Re-entry: a design partner demands listings as first-class evidence

NWI wetlands · RRC wells & pipelines · licensed market series layers post-launch

Ring-2 catalog members not in the ruled TX launch layer set (StratMap parcels, FEMA NFHL, SSURGO, NAIP refs, Protomaps).

Marked in: Explorer layer panel · Re-entry: per-source descriptor + bake through the coverage registry

Field-inspection mobile flows post-launch

Photo capture on site, parcel-at-point from the truck, candidate confirmation on the go — a designed mobile experience that slots into the existing IA (Subject · Candidates · Home) without new navigation.

Marked in: index — responsive strategy · Re-entry: post-launch add-on per the decisions log (desktop-first ruling)

Ruled — 2026-07-22 (Wave-3 Workspace/Explorer/import contract)

MLS photos as a map layer ruled 07-22

Ruled: stripped from v1. The 🔒 layer row is removed from the Explorer panel; listing photos surface only on the record/media pane, where the embed gate (the four-rights vector) governs them.

Ruled in: Wave-3 #2 (P9) · Re-entry: post-launch layer review (alongside RRC/NWI), contingent on an affirmative display+embed license audit for the MLS feed

"Public records" in Explorer search results ruled 07-22

Ruled: Ring 1 + the firm's own staging lane only. Public-record discovery arrives via connectors → candidates on their sync cadence — never live federated search. The results dock now reads "from your verified database + your candidate lane," and candidate cards are the firm's own staging rows badged by feeder.

Ruled in: Wave-3 #2 (P8) · Applied: Explorer dock copy + result-card framing reconciled the same day

Parcel search in the global palette ruled 07-22

Ruled: bounded out of v1. The Ctrl K palette searches jobs, comps, and actions. Parcels live in county-sharded artifacts, and a keystroke-latency surface over them needs a search-index sidecar that hasn't been ruled or costed — Explorer remains the parcel-lookup surface. Topbar placeholder copy reconciled across all pages.

Ruled in: Wave-3 #2 (P3) · Re-entry: the search-index sidecar ruling, when Explorer telemetry shows parcel/address lookup demand

Designed-for but dormant — the hooks already exist

Comp co-op — contribute-to-access sharing dormant

Cross-tenant comp sharing, opt-in and contribution-based. Parked for v1 by ruling, but the schema ships ready day one: per-record sharing-consent (default OFF), provenance, contribution lineage — so the co-op is a feature later, not a migration. Acres.com selling confirmed TX comps re-based the moat language; the whitespace is no longer uncontested.

Lands: Comps + Settings · Re-entry: post-launch, with the provenance-derived poolable flag wired · Source: product brainstorm §6a / decisions log · design-validation (moat)

Trainee program — experience log & supervisor sign-off dormant

The full pipeline feature behind the trainee role: supervisor linkage, an hours-by- property-type experience log, and supervisor sign-off in the shape state boards require for licensure upgrade. No incumbent treats the trainee pipeline as a first-class feature, and the industry's aging demographics make it a real wedge for growing firms. v1 ships only the non-signing assist participant + certification disclosure (gap-analysis C1, option C); this program builds on top of those participant rows plus the audit trail.

Lands: Settings · People & roles + a per-trainee log surface · Why parked: a product of its own — state-form reporting doesn't belong in launch scope · Re-entry: design-partner demand from firms with trainees, post-launch · Source: gap analysis C1 (option D)

Workflow taskboard dormant

Tracker board, status chips, drag-to-move, activity log — deliberately deferred at kickoff; returns as an add-on pack. The event log and job graph are its hooks; Home's needs-attention feed carries the daily load meanwhile.

Lands: an add-on pack (workspace seam) · Re-entry: demand after launch · Source: product brainstorm §4f / decisions log

Per-tenant MCP endpoint dormant

"Connect your own AI tools to your comp database" — machinery proven, parked post-launch; needs bridging to Firebase identities when it returns.

Lands: Settings · Re-entry: post-launch ruling · Source: decisions log 2026-07-19

Native DCF engine dormant

Full Argus-style DCF stays a partner-import boundary until commercial pack v2 (Wave 4); external-schedule import keeps DCF reports producible meanwhile. The Dallas GSA exemplar pins the rendering ceiling long before the engine exists.

Lands: commercial-income pack v2 (analysis seam) · Re-entry: Wave 4 · Source: canonical exemplars

Real-time co-editing (CRDT/OT) dormant

Launch is single-active-editor with a visible, stealable turn lease + presence. True simultaneous co-editing is wanted later; the provider design must not foreclose it.

Lands: Report Studio providers · Re-entry: post-launch demand · Source: decisions log 2026-07-20

Groundsworth · prototype v2.1 (navigation) · parking lot · site map · gap analysis