Purpose
Provide browser-based calculator demos and utilities that run without backend dependencies.
Current state
Last touched: 2024-09-16. Functionality and completeness: Demo calculators exist; documentation is minimal.
Next step
Add baseline automated tests to cover critical flows; Add CI pipeline for build/test/lint; Document deployment/runtime environment (or add Dockerfile); Document interfaces (CLI flags, API endpoints, file formats); Add structured logging and basic health checks.
Interfaces
Outputs- Rendered HTML output and calculated values
Reality to Action trace
Reality IngestionNot in scope.
Canonical StorageNot in scope.
Automation EnginesNot in scope.
Human InterfacesContributes in this stage.
Operational AdoptionContributes in this stage.
Core workflow
TBD. Document the 5-10 steps that define the core workflow.
Operational notes
Constraints and scars
- Browser-only; no server-side validation or persistence.
Reliability posture
Failure modes and safe behavior: JavaScript errors result in missing calculations. Idempotency / retries / batching behavior: Client-side recalculation is idempotent.
Observability
- Logs: Browser console only
- Metrics/health checks: None documented
Security and privacy
Recommended guardrails: Review config handling, avoid committing secrets, and document access controls.
Ownership
OwnersJosh Barton
UsersJosh Barton (owner)
WebCalculator
Architecture & Major Components
High-level diagram (text):
- Entry/trigger -> core logic -> outputs (details per docs below)
Entry/trigger
→core logic
→outputs
Entry points: WebCalculator/BondCalculator.html, WebCalculator/WebPageCalculatorDemo.html
Top-level folders: none (files only)
Key abstractions: HTML forms and client-side calculation logic
Setup / Build / Run
- Build system(s): None (static HTML)