Public page availability
3 / 3 responding
- HomeHTTP 200
- Studio operationsHTTP 200
- Client workspaceHTTP 200
Successful responses also match the expected page title.
Studio operations / Site status
Studio,
at a glance.
Page availability, architecture grades, verification results, and the work still ahead. Every result is tied to its latest check.
Explore site healthSoCAS 0.1 assessment
69/ 100
Provisional D
An architecture score for this source snapshot. Not certified.
- Semantic review
- 24 / 30
- Structural checks
- 45 / 70
Local browser verification needs refreshing
These observations were recorded for an earlier source snapshot and must be rechecked. Checked 2026-09-10 18:10:47 UTC.
Analytics blocked. Earlier production check (2026-09-10T07:16:41.970Z): Cloudflare’s injected analytics beacon was blocked by the site’s content security policy during production browser checks. Page controls and menu navigation passed.
Latest check / 2026-09-12 14:38:56 UTC
Site health
A saved read-only check of production pages. This is not continuous uptime monitoring or verification of signed-in customer workflows.
Local verification
12 / 12 suites passed
- Site Agent and regressionsPassed
- Backend unit testsPassed
- Assessment integrityPassed
- Shared billing policyPassed
- Persistence and account adaptersPassed
- SDK boot and callable contractsPassed
- Reusable UI componentsPassed
- Backend entry bindingsPassed
- HTTP validation boundaryPassed
- Portfolio finance and scenario modelsPassed
- Agreement and workspace workflowsPassed
- Service workflows and domain rulesPassed
2 emulator-only tests skipped. These checks describe the local source snapshot.
Needs attention
Evidence & architecture
- History evidenceMissing
- Concerns tested in isolation0 / 6
- Unresolved tooling imports0
- Concerns in import cycles0
Backend service health, live billing and email delivery have not been independently checked here.
History evidence is missing.
This checkout has no eligible Git history. That measure earns 0 of 15 points, and certification remains unavailable. Those missing points are separate from the architectural issues found by the reviewers.
01 / Meaningful separation
Semantic review
Three isolated reviewers rated the same code independently. Each measure uses their median rating, weighted by the shared rubric.
| Measure | Review ratings | Earned |
|---|---|---|
| Responsibility coherence | 4 / 4 / 3Median 4 of 5 · 94% confidence | 5.6 / 7 |
| Boundary appropriateness | 4 / 4 / 4Median 4 of 5 · 94% confidence | 4.8 / 6 |
| Conceptual leakage | 4 / 4 / 4Median 4 of 5 · 94% confidence | 4 / 5 |
| Reasons-to-change isolation | 4 / 4 / 3Median 4 of 5 · 94% confidence | 4 / 5 |
| Naming and abstraction alignment | 4 / 4 / 4Median 4 of 5 · 94% confidence | 3.2 / 4 |
| Exception legitimacy | 4 / 4 / 4Median 4 of 5 · 92% confidence | 2.4 / 3 |
Ratings use a 0–5 scale. Confidence is the lowest confidence across the three reviews for each measure; it is not a probability that the software is correct.
02 / What would improve it
Make reuse go deeper.
Billing policy is now shared at its source, page data access uses adapters, and backend entry points dispatch to feature services. The next work addresses the remaining broad controllers and evidence gaps.
- 01
Separate page workflows.
Agreement editing, preview billing and checkout now own their state and explicit dependencies. Continue separating project delivery, scheduling and account workflows from the broad Operations and workspace controllers.
- 02
Isolate service transactions.
All six concerns have representative isolated behavior tests. Yearly billing requests and appointment reminders also have concurrency checks. Extend the sample through agreement execution, payment changes and the remaining page workflows.
- 03
Build real history evidence.
Future versioned changes can demonstrate whether each concern changes independently. This checkout has no eligible history; new or synthetic commits cannot recreate it.
03 / Measured boundaries
Structural checks
262 authored JavaScript files assessed, with 148 cross-concern imports. A clean layer graph cannot prove that a large module has one coherent job.
| Measure | Earned |
|---|---|
| Declared dependency conformance | 25 / 25 |
| Absence of cross-concern cycles | 10 / 10 |
| Historical change isolation | 0 / 15 |
| Test isolation | 0 / 10 |
| Interface containment | 10 / 10 |
Test evidence: 12 of 12 selected suites passed. This is bounded test evidence, not proof of complete test isolation.
04 / Method and limits
What is SoCAS?
Separation of Concerns Assessment Standard is our custom architecture scorecard. It combines 70 structural points and 30 semantic points. It is not an external certification.
Read the scoring rules and evidence limits
Grades: A ≥ 90, B ≥ 80, C ≥ 70, D ≥ 60, E below 60. A also requires at least 24 semantic points.
- An unapproved forbidden dependency caps the result at B.
- An unapproved cross-concern cycle caps the result at C.
- Missing evidence or unresolved low-confidence AI findings prevent certification.
- An A requires at least 24 of 30 semantic points.
Reviewer disagreement above two rating levels or confidence below 70% requires human review.
- Generated *.min.js, vendored SDKs, showcase artifacts and dependencies are not authored source.
- Literal module imports, exports and require calls are parsed. Computed imports, global adapters, HTML script composition and remote calls require semantic review.
- The layer graph does not detect responsibility mixing inside a single module or concern.
- 0 of 6 production concerns have independently reviewed representative isolation evidence. Partial concerns earn no credit. Isolation review is missing or belongs to an earlier source snapshot.
- A custom architecture assessment, not external certification or a security, accessibility or performance audit.
- Semantic review covers authored browser and backend JavaScript; new assessment tooling is validated by its own tests.
- Scores are a dated source snapshot, not a continuous monitor.
- No Git history is available in this Studio checkout. The missing historical measure earns 0/15; timestamps and synthetic commits are not substitutes.
Literal dependency parsing found 7 computed imports and 0 unresolved local imports. Computed imports and global service adapters are outside the automatic graph and require manual review.
This public summary contains aggregate engineering findings only. Detailed review evidence stays outside the published site. The score is regenerated during a local assessment; no scheduled monitoring has been enabled.