Modeled connectivity
Follows explicitly recorded fibers and ports. Green does not prove a physical splice or live service.
FIBERATLASTry FiberAtlas Menu
RC2 / UNDER THE HOOD
The checks.
The results. The limits.
We want you to see what backs this workflow preview. These are dated software checks with a defined scope; the signed RC2 package receipts and the bounded acceptance record below preserve the original full-suite failures as historical evidence.
1,461feature-gate tests passed
0feature-gate failures
4package receipts verified
FiberAtlas RC2 — New Splicing Workflow & UI Face Lift · 0.1.0-rc.2 · Feature gate: October 13, 2026
Release verification
| Check | Result | What the evidence shows | Scope |
|---|---|---|---|
| RC2 feature gate | Passed | The RC2 feature gate passed 1,461 tests with 0 failed and 18 pending. The broader source receipt records 2,222 passed, 13 historical baseline failures, and 25 pending; those failures remain disclosed rather than counted as passes. | Current source; the skipped checks are opt-in visual, PDF and fixture-generation evidence. |
| Package identity & signing | Verified | Full and Trial Setup and Portable have valid timestamped signatures from John Philipe Kemmler. | Four exact Windows x64 packages. |
| Edition controls | Verified | Full keeps its trusted license key and requires activation. Trial keeps its original device start date and 14-day editing limit. Application payloads match between editions. | Existing licensing behavior and package identities. |
| Protected upload | Verified | Each uploaded file was downloaded through the owner-protected path and its full bytes matched the published SHA-256. | No visitor access rules changed. |
| Windows install, uninstall and device upgrades | Historical baseline retained | Prior release acceptance is historical. Broader native acceptance on these exact bytes remains open. | No fresh Windows Sandbox or antivirus-scan claim. |
HOW THE NETWORK LOGIC IS CHECKED
Known inputs. Expected outcomes.
Synthetic fixtures let us check failures as deliberately as successes. Expected assignments are specified independently of the trace result. These examples are fictional software tests.
| Scenario | Expected modeled result | What it checks |
|---|---|---|
| Three correctly connected services | 3 passed | Recorded paths reach their intended sources. |
| One explicit cut | 2 passed / 1 failed | A broken path must not look connected. |
| Two swapped assignments | 1 passed / 2 failed | Reachability alone is not the correct assignment. |
| One missing assignment | 2 passed / 1 incomplete | Missing intent stays incomplete. |
| 100 and 1,000 service fixtures | Each documented assignment checked | Bounded synthetic scale and cancellation cases; not a device performance promise. |
| Supported 1 × 32 PON | Explicit feeder-to-branch paths | Reverse tracing stays on the selected branch rather than lighting sibling services. |
Regression coverage also exercises recorded versus draft state, occupied and invalid connections, stale results, saved-run integrity, field-evidence import and history, persistence, and export disclosure. The feature-gate count is a software assertion count, not a count of field-tested networks.
Three results that stay separate
Modeled optical loss
Calculates with the selected wavelength, documented components, lengths and profile. Missing inputs remain unknown.
Measured evidence
Preserves user-entered or imported observations. It does not issue engineering or owner acceptance.
Where more testing is needed
- Broader Windows configurations, display scaling, and install/upgrade combinations.
- Shared drives, multi-workstation locking, and real concurrent users. RC2 support is bounded to local project storage.
- Physical printers and driver-specific layout behavior. PDF output has been exercised; a printer pass is separate.
- Long practitioner workflows with realistic projects. Synthetic scale tests are not a guarantee for all project sizes.
- Optical profiles, manufacturer data, owner criteria and real field evidence. The starter catalog is incomplete.
There is no overall field-validation, engineering-approval, or production-certification claim here. Tell us which environment or workflow you can help test →
Exact release identity
- Public label
- FiberAtlas RC2 — New Splicing Workflow & UI Face Lift
- Embedded app version
- 0.1.0-rc.2
- Source commit
66c4ceea568658f933850d056fd374b3dc62ac66- Build ID
fa-0.1.0-rc.2-b4e13b1388196cdd- Setup SHA-256
3EA0E014B5B0A205EC0D32970F47425778D0AEA27DEECC0A065016C283C8B85B- Portable SHA-256
7DE9681B8DE4E39F8685F02280DF7B244050131E71A44A94DD8DB4801455F6FF
The embedded app version and executable filenames use 0.1.0-rc.2. The RC2 evidence record includes Full and Trial identities, signatures, runtime gates, feature tests, and the disclosed historical baseline.
Read it. Try it. Challenge it.
Use the reference user manual to try a small fictional project, then share what you find.
Prepared from current source-check receipts and exact package verification. The original full-suite historical failures are disclosed in the RC2 evidence record and are not represented as passing. The current print renderer does not show new riser and span overlays.