Security candidate advances; release still gated
The newer candidate passed four exact-revision CI checks. Local compliance audit and recovery coverage also advanced. Production acceptance and credential integration remain open.
NXTDEAL / BUILD JOURNALREPORT 005 · October 18, 2026
State of
the Build.
The foundation is built. The next job is proving it in daily dealership work.
PRE-BETA · IN ACTIVE DEVELOPMENT
THE CURRENT PICTURE
Broad foundation.
Focused next steps.
The security candidate has new passing CI evidence, and local compliance, Parts and desktop testing have advanced. Previously released app features remain distinct from these newer candidates. No beta readiness gate is newly closed; outreach evidence is unavailable for this review.
01 / THE PATH FORWARD
From working software
to a working dealership.
Open any milestone for its exit conditions.
Position shows sequence, not a completion percentage.
01Implemented
Build the foundation
Department workspaces, the shared app framework, MySales and the public website exist. This milestone describes implementation breadth, not approval of every workflow.
02In progress
Review real workflows
Inventory/recon handoff and receiving-role changes have passed local checks, with their browser journey still pending. Native Lab planning and history improvements are released. Complete pilot-role acceptance remains open.
03In progress
Prove production readiness
Security and payment review tools are deployed. Isolation, restore evidence, access policy and operational ownership must be demonstrated for the chosen beta scope.
04Next
Run an invited pilot
Select a dealer, name supported workflows and permitted data, complete onboarding and exercise a full working day with support and rollback available.
05Gated
Open the scoped beta
Release only the workflows with recorded acceptance. Finance, payments and OEM programs have separate approval paths.
02 / WORKSTREAMS
What exists. What’s reviewed.
What comes next.
Each workstream has a different readiness level.
Expand a card to see the evidence and remaining work.
● Live / implemented● Active review / development● Dependency / release gate
01Built · review underwayCore dealership platform
CRM, sales, inventory, service, finance, marketing and administration share a working platform.
Built so far
Department workspaces, operational boards, shared records, role navigation and API services are implemented. Reception, Sales and Service have dedicated app surfaces.
Reviewed so far
Local Parts returns now include backend handling and an inline return workspace. A bank-feed explanation also addresses empty simulated results. Owner records report 941 scoped backend checks and 334 frontend checks; the complete backend suite did not finish within its time limit. Inventory and Parts browser acceptance remain open.
Next milestone
Finish the pending inventory browser walkthrough, consolidate the candidate, then complete full-day acceptance across pilot roles and departments. No new deployment is evidenced for this local core-workflow candidate.
Evidence: October 18 repository-head reconciliation and Hermes run records. The checkpoint contains a mismatched full commit identifier; the actual repository head was used. These scoped owner results do not establish full-current-code or production acceptance.
02Live · acceptance expandingMySales
A standalone personal sales desk, public showroom and lead workflow are live.
Built so far
Personal contacts, notes, follow-ups, pipeline, public profiles, inventory, inquiries, appointments, QR sharing, templates, campaign links, goals, referrals, reports and export/recovery. New live additions include multi-photo galleries and cover selection, structured vehicle details and search, and vehicle-specific Live kits with public links, QR cards and manual sharing.
Reviewed so far
Previously released desktop reliability improvements remain the last recorded live milestone. Today a test-only email verification and recovery candidate was pushed; exact-revision CI passed 232 backend and 137 frontend checks, plus isolation and persistence checks. That candidate is not a new runtime deployment. No new runtime release is evidenced in the October 18 review; the owner records 309 full frontend tests for the current test-only source. Physical-device and on-device model acceptance remain open.
Next milestone
Complete physical-phone photo picking, downloads, QR scans and installation, plus local-model acceptance. Authorized dealer CRM delivery and optional domain/email connections remain outstanding. Saved inventory is not guaranteed live stock.
Evidence: October 18 source reconciliation against the October 17 test-only candidate and CI evidence. Earlier live acceptance remains historical.
03Controls live · evidence openSecurity & compliance
Containment and review tools are deployed; production readiness remains a separate gate.
Built so far
Previously released containment and review tools remain available. The newer security candidate extends access controls; local compliance work adds audit recording and recovery coverage. Neither new candidate is reported deployed.
Reviewed so far
The latest pushed security candidate passed all four exact-revision CI checks, including backend, frontend, isolated kiosk acceptance and container checks. Its owner records 1,025 local security tests. New local compliance audit work has 115 scoped owner-reported passes; a separate recovery run records 56 passes. Earlier independent compliance checks validate an older candidate, not all newer changes.
Next milestone
Integrate and review the candidate credential routes, complete multi-worker and Linux staging acceptance, secure operational provisioning, full role/tenant acceptance, recovery evidence and external approvals. Recent CI/access evidence supersedes older blanket billing blockers; each new release still needs its own acceptance.
Evidence: October 18 current repository heads, GitHub candidate checks and Hermes checkpoint/run evidence. Live acceptance, coordinated provisioning and credential cutover remain separate gates.
04Roadmap · externally gatedTexas forms & BHPH
Texas is the first planned forms rollout; no contracting jurisdiction is enabled by the new gate.
Built so far
Execution restrictions and a staged roadmap covering transaction scope, forms inventory, calculations, signatures, servicing and pilot acceptance.
Reviewed so far
High-risk contracting, identity, payment and signature paths received an initial source review. This establishes the work order, not legal approval.
Next milestone
Confirm the pilot transaction structure, select qualified reviewers and form sources, establish rights, then validate the packet, calculations, delivery and servicing. No transaction-capable launch date is committed.
Evidence: Plan NXTdeal compliance roadmap · Texas-first delivery sequence and forms/OEM handoffs.
05Live improvements - acceptance continuesDealership Lab
Dealership modeling is moving into a more connected native planning workflow.
Built so far
Native setup and operating editors, scenario/history workflows, finance detail, goals, reviews and procedure checkpoints. Latest deployed planning improvements make keep/discard choices explicit and preserve goal forms after a failed history load.
Reviewed so far
Previously deployed native planning improvements remain the last recorded live milestone. The committed print fixture has seven checks across six synthetic PDF pages; it does not establish full-app visual pagination. Further local CSS and cancel-path test edits are uncommitted; the owner records 37 Lab journey checks. Older CI does not validate those working changes.
Next milestone
Complete authorized closed-period source integration, dealership membership/shared-review decisions, remaining full-shell journeys and actual PDF pagination acceptance. No live connector or complete integration certification is claimed.
Evidence: October 18 current working-tree review, Hermes Lab checkpoint and dated print-fixture evidence. Real membership/source adoption and full-shell acceptance remain open.
06Implemented · scope reviewAI, dealer bridges & OEM integrations
Chrono and assistant connection foundations support the platform’s direction; each live integration needs its own evidence.
Built so far
Chrono-related platform capabilities, assistant connection paths, agent permissions and dealer data-bridge foundations are present in source and handoffs.
Reviewed so far
Integration and agent boundaries remain part of the compliance inventory. No new provider or OEM approval is verified. Tagged Codestral and HF engineering helper monitoring records zero attempts, responses or tokens today and cumulatively across all eight streams; no linked completed contributions are recorded.
Next milestone
Verify supported workflows, scoped authorization, revocation and provider acknowledgments. Name the first OEM program and obtain its required access before production use. Helper throughput benefit is not yet demonstrated; bounded cost controls remain in place.
Evidence: October 18 refreshed helper metrics, empty contribution ledgers and current integration handoffs; setup qualification is excluded from completed engineering.
07Candidate prepared · acceptance openChrono platform
Synthetic commercial subscription tracking has a tested source candidate; hosted release acceptance remains open.
Built so far
The subscription candidate is committed and pushed. Candidate and recovery packages are prepared with synthetic lifecycle and containment checks. Payment and provider execution remain disabled.
Reviewed so far
The October 17 independent commercial rerun passed 46 tests at the committed candidate. Today there are further uncommitted commercial-summary and test edits; those earlier results do not validate the new working tree. No new verified hosted release is recorded.
Next milestone
Finish and validate the working changes, reconcile remote source, verify backup/restore and held startup, and complete exact-candidate hosted acceptance before a manual release.
Evidence: October 18 source and working-tree reconciliation; October 17 independent candidate evidence and Chrono handoff.
08Local tests · packaging gatedChrono desktop Engine
Desktop approval and request-boundary test coverage has expanded locally.
Built so far
Local test commits extend the existing Engine approval-flow and desktop bridge coverage. This is test work on an inherited implementation, not a packaged product release.
Reviewed so far
The latest owner run reports 45 scoped Python checks, including new request-validation cases. Earlier simulated and component checks are not physical-device or packaged Windows acceptance. No release push or deployment is recorded.
Next milestone
Reconcile the desktop candidate with upstream source and complete packaged Windows, real-browser and supported CRM acceptance. Local-model relationship and identity qualification remains unresolved; unattended migration is not approved.
Evidence: October 18 current Engine commit and run records. Inherited tracked/untracked work remains separate from new tests.
09Built · selective acceptanceDepartment & customer apps
Staff apps and kiosk foundations exist; customer-sensitive workflows have their own release gates.
Built so far
Role-oriented app entry, reception, sales and service task surfaces, customer-facing routes and restricted kiosk work.
Reviewed so far
October 10 kiosk checks used a real browser with an isolated backend, fictional identity and durable check-in evidence. The review explicitly excludes production and physical-device activation.
Next milestone
Finish device/origin review, customer verification and complete role journeys. Do not treat a working screen as approval for autonomous end-to-end retail.
Evidence: Review NXTDeal project status · October 10 readiness evidence and October 11 daily-workflow review.
10Live · launch preparationWebsite & beta onboarding
The public website, pricing direction and beta-interest path are in place.
Built so far
Product and industry pages, security requirements, founder story, blog, MySales positioning and a beta-interest form. Marketing signup conversion tracking and welcome-email integration have also been released.
Reviewed so far
The public website retains the prior homepage metadata and SEO package. Current outreach status could not pass freshness checks on October 18, and the available morning Sent-copy verification is dated October 16. Today's introduction, drip and Sent-copy counts are unavailable, not zero; no fresh delivery or reading claim is made.
Next milestone
Reconcile outreach receipts separately. Finalize pilot support, terms, permitted data and onboarding. Interest-list enrollment does not grant beta access.
Evidence: October 18 mirror refresh and canonical receipt-date review. Historical outreach receipts remain dated in the change log; they are not current send totals.
03 / BETA READINESS
The gates that matter.
A limited, invited dealership beta for approved CRM, inventory and daily staff workflows. This estimate excludes live contracting, regulated finance, payment processing and unapproved OEM connections.
01Release consolidationOpen +
One identified candidate with the intended workspace, API and app versions; current builds and scoped regression checks. Locally reviewed dealership and Lab candidates still need consolidation; additional security changes await release validation.
Accountable role: Engineering02Production security evidenceOpen +
Approved access policy, tenant isolation, encryption, restore exercise and evidence for the workflows being admitted.
Accountable role: Engineering + security owner03Workflow acceptanceOpen +
Complete real-role journeys including failed saves, permissions, recovery and record handoffs.
Accountable role: Engineering + pilot dealer04Data & onboarding termsOpen +
Permitted data, ownership, provider access, retention, notices and acceptance captured for the actual pilot scope.
Accountable role: Founder + qualified reviewers05Pilot operationsOpen +
Named pilot, support and incident contacts, monitoring, rollback and a supervised full-day trial.
Accountable role: Founder + pilot dealer06Transaction scope approvalSeparate gate +
Form rights, reviewed rules/calculations, signatures, settlement and servicing. Required for transaction beta; excluded from the limited-beta estimate.
Accountable role: Qualified reviewers + engineeringHow we estimated About 4–8 weeks +
Development planning judgment, originally set October 14 and reviewed October 18. The November 11–December 9 window is unchanged, not reset daily. Allow roughly 1–2 weeks for consolidation and scope, 2–4 weeks for production evidence and role acceptance, and 1–2 weeks for a supervised pilot, with overlap. This requires sustained engineering capacity, a named pilot and timely review decisions. Release validation and consolidation remain unresolved, so the earliest part of the window is at risk.
If production evidence or pilot acceptance remains open, the window moves. A transaction-capable Texas/BHPH beta has no defensible date until form rights, qualified review, calculations and servicing acceptance are resolved.
04 / THE LATEST NOTES
Movement worth recording.
Core and desktop tests progress locally
Parts returns and clearer empty bank-feed results are committed locally with scoped owner-reported tests. Chrono Engine gained desktop boundary coverage. These are not new production releases.
Lab and Chrono working changes remain unverified as releases
Lab has further uncommitted CSS and cancel-path coverage; Chrono platform has uncommitted commercial changes. Older candidate checks do not certify these newer working trees. MySales remains at its previously reviewed test-only candidate.
Outreach unavailable; engineering review published
Current outreach receipts and October 18 Sent-copy verification are unavailable. Verified engineering progress is reported independently. No current send totals or zero-send assumption is substituted for missing evidence.
Helper usage unchanged; benefit not demonstrated
Fresh tagged monitoring across eight streams records zero Codestral or HF helper attempts, responses and tokens today and cumulatively, with no linked completed contributions. Main engineering work is not attributed to these helpers.
Forecast unchanged; no readiness gate closed
The original November 11-December 9 limited-beta planning window remains conditional, with earliest dates at risk. Production evidence, real-role acceptance and pilot selection remain open; Texas and OEM approvals remain separate dependencies.
Candidates pushed; deployment remains separate
MySales test coverage, security, compliance, Lab print checks and Chrono platform work advanced through source publication and scoped validation. No new application production release is claimed by this review.
Independent candidate checks completed
Isolated reruns passed 27 compliance tests and 46 Chrono commercial tests. MySales exact-revision CI passed its backend, frontend, isolation and persistence checks. Counts describe separate scoped runs and must not be added into an overall readiness score.
Outreach evidence remains a separate limitation
Current outreach receipts were not reconciled for this report. Previous send totals are historical; this edition makes no fresh delivery claim. Verified engineering progress can still be reported.
Forecast unchanged; acceptance gates remain open
The original November 11-December 9 limited-beta planning window is unchanged, with its earliest dates at risk. Release consolidation, production evidence, real-role acceptance and pilot selection remain open.
MySales saves and search reviewed live
Template search, clipboard recovery and saved-record visibility releases passed checks. Desktop acceptance confirms saved templates and vehicles remain visible after filter-changing edits. Physical-phone acceptance remains open.
Lab planning and history improvements deployed
Native keep/discard controls and recovery after failed history loads are released. Source authorization, shared review and PDF pagination remain separate unfinished work.
Security releases and local Hermes candidates
The prior release window delivered additional access and administrator safeguards. Overnight Hermes work adds locally tested scope and credential/audit improvements; neither overnight candidate is deployed. No readiness gate is newly closed.
Morning outreach receipts verified
Morning and cumulative Hermes counts: 3 accepted introductions, all 3 verified in Sent, and 70 verified listmonk drip sends. Delivery and reading are unconfirmed. Sending stopped on an uncertain campaign-creation result pending reconciliation; no claim is made that these sends occurred at exactly 6 a.m.
AI helper benefit remains unproven
Tagged security and compliance monitoring records zero Codestral or HF fallback attempts, responses or tokens today and cumulatively, and no linked completed contributions. Setup qualification is excluded. Bounded cost controls remain in place; no throughput benefit is yet demonstrated.
Forecast unchanged; gates still open
The original November 11-December 9 limited-beta planning window remains conditional, with the earliest dates at risk. Core acceptance, production evidence and pilot selection remain open. No newly verified Texas legal/forms approval or OEM access closes those separate dependencies.
MySales inventory and sharing expand
Photo galleries, structured vehicle search and vehicle-specific QR/Live kits are deployed and desktop-reviewed. Physical-phone acceptance remains open.
Compliance safeguards released; further review open
Consent and campaign reporting safeguards advanced in production. Additional access-control work remains locally tested, with release validation and readiness evidence outstanding.
Core workflows and Lab advance locally
Sales, recon and inventory recovery reviews progressed. Lab procedure locking and historical editions passed component/API browser checks. These candidates are not yet deployed.
Beta forecast retained, with schedule risk
No beta gate closed in this review. The original November 11–December 9 planning window remains conditional, with its earliest dates at risk while release consolidation, production evidence and a named pilot remain open. Texas transaction approval and OEM access have no newly verified progress.
Marketing onboarding releases
Signup conversion tracking and welcome-email integration are released. Joining the interest list still does not grant beta access.
MySales reliability releases
Sharing recovery, inventory browsing and profile draft protection are reported live. Physical-device acceptance remains open.
Compliance controls advance
Review tools and successive MFA safeguards are deployed. Production evidence and Texas packet review remain outstanding.
Workflow and Lab review continues
Inventory recovery and native Lab operating-editor checkpoints passed scoped local tests; those improvements are not yet reported deployed.
A REPORT YOU CAN READ WITH CONTEXT
Prepared by Development from current repository heads and working changes, Hermes checkpoints and dated run records, historical source chats and exact-revision CI. The morning brief and preparation inventory were stale at the start of this late run; current sources were reconciled and the brief refreshed. Owner-reported tests are labeled and are not an independent audit. Built, tested, pushed, deployed and approved remain separate. Missing optional outreach evidence is disclosed without blocking verified engineering coverage.
Scheduled for a daily 6:00 a.m. Central review with daylight-saving changes. This October 18 run began at 11:35 a.m. Central; no timely 6 a.m. publication is claimed. The timestamp records the actual evidence review, not a product deployment. Desktop availability and validation affect publication time.
FOLLOW THE BUILD. HELP SHAPE THE BETA.
Be part of what comes next.
Join the interest list. We’ll share access details when the approved scope is ready.