NOWEDGE’s website is beginning to show the development process as well as the instrument. The first Building NOWEDGE entry and a prominent homepage link now form the starting point for that history.
What changed?
Why did it change?
What happens next?
A home for the build journal
The brand-experiment site now has an In Production indicator, a homepage build-note feature, and a complete September 13 entry.
The first version uses structured content to render the story, supporting images, lessons, and next steps. This website update was deployed to the existing NOWEDGE brand experiment.
Make countdowns agree
A demo exposed a small but trust-eroding inconsistency: the primary ring showed 28 seconds while NEXT still read “in 1 minute.” Both displays described the same event, but independent rounding made them feel disconnected.
The accepted rule is that NEXT should display seconds below one minute and derive from the same countdown source. The capture demonstrates the problem; implementation still needs to be validated.
Give the approach to the open distinct states
The accepted sequence calls for a blue Countdown to the Open during the final ten-minute window, followed by a yellow Countdown to the Opening Bell during the final two minutes.
At 6:30 AM PT, THE OPEN retains the existing ring as the warning instrument for the first minutes of regular trading.
- 6:20–6:28 AM PT · Countdown to the Open · blue
- 6:28–6:30 AM PT · Countdown to the Opening Bell · yellow
- 6:30 AM PT onward · THE OPEN · preserve the ring clock
Let visitors play through the product
A website scenario player could drive NOW/NEXT, the Event Horizon, Candle, and alerts with one simulated clock.
The supplied Candle demo illustrates the kind of interaction to explain: a simulated price moves through a known reference and changes the displayed state. The web player remains a proposal.
Show the project as it evolves
The site will explain what is being built for personal use, how Codex helps implement it, and what is being learned at the desk.
Historical entries should distinguish decisions, tests, and completed work so readers can follow the actual evolution.
A development record has to earn trust, too.
- The build journal needs the same care about truthfulness as the product.
- An approved narrative is not, by itself, evidence that the feature described in it has shipped.
- Related timing surfaces need one authoritative source of truth.
Turn the decisions into tested behavior.
- Validate the complete 6:20–6:32 AM market-open sequence.
- Define one reusable scenario format for the Event Horizon, Candle, EDGE, and alerts.
- Continue reconstructing the earlier project history from dated evidence.
ProductIn Production
Primary hardwareXENEON EDGE
DevelopmentCodex-assisted
TestingPersonal trading workstation
AvailabilityNot yet released