Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Reference Examples

The server can use CE-RISE examples as examples, then generalize from them.

The first curated reference example is the Digital Passport System Local Demonstrator. It is useful because it shows existing CE-RISE components working together locally, but its concrete products, payloads, local no-auth settings, storage choices, and ports are not defaults for adopters.

Its component set is not a required architecture. Adopters can reuse individual CE-RISE services or models alongside external components and choose another deployment workflow. Only the selected CE-RISE interfaces are within the assistant’s assessment scope.

Its three commands demonstrate different workflows:

Command in the demonstrator repositoryWorkflow
make demoChair passport validation, persistence, read-back, and invalid-input rejection
make demo-re-indicatorsAll five published laptop RE indicators and invalid-input rejection
make demo-see-impactsPV input validation, one calculation returning all 25 indicators, numerical comparison, and validation/persistence/read-back of the complete Integrated LCA output

The separate make validate-see-impacts command checks readiness, input schemas, a saved output, and invalid-input rejection. It does not run the calculation or persist records.

For another product, reuse the validation, calculation, comparison, and persistence sequence with that product’s foreground records and functional unit. SEE uses its released image’s shared background and methods; the PV example does not require an adopter to prepare a product-specific Brightway project.

Use generalize_reference_example to extract reusable patterns such as:

  • declaring the adopter’s scope and value-chain roles;
  • selecting required CE-RISE services and optional services;
  • adapting the model registry catalog;
  • preparing adopter-specific valid and invalid payloads;
  • exercising the intended record lifecycle;
  • turning demo checks into environment-appropriate operational checks.

The result separates:

  • reusable pattern;
  • contextualized action for the declared adoption context;
  • CE-RISE assets to reuse;
  • assumptions from the example that should not be carried over.

This keeps the demonstrator useful without making it a hidden architecture mandate.