Useful systems should make dependencies, decisions, documents and handoffs easier to understand—not harder to trust. Explore working browser prototypes and see exactly what remains experimental.
04 working browser alphas02 design-stage conceptsPrototypes · No production certification
01 / Available to try
Real prototypes. Visible limits.
Four browser-based alphas you can open today. These are working demonstrations, not enterprise deployments, certified compliance systems or production-ready services.
01 / DEPENDENCY INTELLIGENCEWORKING ALPHA · v0.1
Flowglass
See what a change could affect before you make it.
Build and inspect a dependency map. Follow upstream or downstream relationships, find cycles or missing documentation, and export a readable impact review.
Graphs are supplied or modeled manually. No Power Automate or SharePoint tenant scanning, automatic discovery, cloud sync or production-risk certification. Data stays in the current browser unless exported.
02 / DOCUMENT DIAGNOSTICSWORKING ALPHA · v0.1
FilingProof
Find technical PDF problems before filing.
Examine PDF text layers, form fields, embedded attachments and selected reference checks with explicit not-evaluated findings.
Not a court filing service or acceptance validator. No legal advice, OCR, complete redaction checks, malware scanning or certification. Files are reviewed locally; a pinned PDF parsing library is fetched from a third-party CDN.
Design fictional case workflows on a draggable canvas, connect processing steps, and test conditional priority routes. Then run synthetic cases through dependency-checked tasks, exceptions, assignments, and a browser-local activity trail.
Drag-and-connect workflow designer
Priority-based conditional routing at intake
Fictional cases, task validation and portable exports
Fictional data, fictional deadlines and synthetic business rules only. Not connected to courts, e-filing, identity systems or protected records. No authoritative legal workflow guidance or tamper-evident audit ledger.
RUNBOOK / DECISION ROUTES01 · START↓02 · DECIDE↓03 · HAND OFF
04 / OPERATIONAL KNOWLEDGEWORKING ALPHA · v0.1
Handoff Atlas
Turn a complicated procedure into a navigable path.
Author branching runbooks, validate routes, publish local revision snapshots and guide an operator through decisions with portable handoff records.
Browser-local demonstration with sample procedures. No team accounts, encrypted backend, verified operator identity or signed audit log. Do not enter sensitive operational or case records.
Flowglass, FilingProof and CourtFlow use existing conceptual promotional artwork, not screenshots or verified real court records. Handoff Atlas has a schematic procedure illustration. Every launch link opens the actual working browser alpha.
02 / Design lab
Next, not yet.
Two proposed products with defined problems and validation gates. These are specifications and design explorations—there are no public applications to launch.
A proposed evidence-linked document review workspace for policies, specifications and long-running project records. It would make supporting passages, decisions, revisions and unresolved contradictions inspectable.
Claim-to-passage traceability
Decision and change records
Stale-source and discrepancy review
Planned workflow and next gate
Register sources and decisions; link specific claims to evidence; compare new versions; export unresolved issues. Next: prototype a source-anchored issue register and evaluate false-positive flags with a human reviewer.
02 / NARRATIVE CONTINUITYCONCEPT · DATA MODEL STAGE
Lorelock
Let the world change without losing its history.
CHARACTERCANONEVENTRULES
A proposed continuity workspace for fiction, tabletop campaigns, sourcebooks and branching stories. It would keep author-approved canon distinct from in-world claims, drafts and spoilers while tracking relationships and timelines.
Canon and provenance states
People, places and relationship maps
Chronology and contradiction review
Planned workflow and next gate
Register accepted references and facts; capture scene outcomes and rule changes; compare new material against established continuity; record approvals. Next: test a continuity schema on one controlled fictional setting.
03 / Development principles
A useful interface is only the start.
01 / TRACEABILITY
Show where it came from.
Make evidence, rules, assumptions and change history visible when decisions matter.
02 / HUMAN CONTROL
Keep judgment with the operator.
Provide reviewable routes and outputs rather than invisible automated authority.
03 / VALIDATION
Prove the critical path.
Separate a functioning prototype from field-tested, secure, supported production software.
Testing / Collaboration
Want to shape what comes next?
Try Flowglass, FilingProof, CourtFlow and Handoff Atlas now. Proofline and Lorelock remain design-stage concepts. None of these are independently certified for professional or regulated production use.