← ExamplesSpecification
Financial specification navigation

Ledger.Server

Financial workspace workflows and project contracts

Open application

Responsibility

Example.fsproj builds Ledger.Server. Model.fs and Routing.fs own URLs; Layout/Application own shared product HTML; Specification/Architecture and ApiDocumentation render the other surfaces; Hosting.fs adapts native forms to Application operations.

Dependencies

  • Ledger.Application and Acme.Components; Giraffe at the HTTP edge.

HTTP surfaces

// GET /examples/application/accounts
// GET /examples/application/accounts/{id}
// GET /examples/specification/accounts/view-accounts
// GET /examples/specification/accounts/view-account?resource=101
// POST /examples/application/accounts/new
// POST /examples/application/accounts/{id}/edit
// POST /examples/application/accounts/{id}/delete
// GET /examples/api-documentation

Rules

  • GET requests SHALL render the product selected by the URL.
  • Specification App-mode links SHALL retain workflow, fixture identity, workspace and docking context.
  • POST requests SHALL accept same-origin URL-encoded bodies of at most 64,000 bytes and map typed operation results to finite redirects.
  • Browser form endpoints and illustrative JSON API contracts SHALL remain distinguishable.
Ledger.Server