Iteration 2

Due: Oct 20, 2026

Planned scope: Research and design

Item	Description
AI proposal	AI requirements, tools and estimated token usage, to send to the stakeholder.
Meetings	Meetings with the stakeholder, the Omerlo CTO and the other companies to validate scope and data access.
Architecture (#28, #29)	Data pipeline architecture, system layers and domain diagram. See Overall Architecture and Class Diagrams.
Entity mapping	Map the entities from each source to the Unified Data Model.
Onboarding	Define the onboarding process.
Verification	Check the design and assumptions before development starts.
Tech stack and ADRs (#15)	Record decisions D1 to D7 and the library choices. See Architecture Decision Records and Infrastructure and Tools. Moved from Iteration 1.
Personas (#31)	Personas that the user story backlog is written for. Moved from Iteration 1.
Problem statement and risks (#32)	Problem statement and the risk register. See Risks. Moved from Iteration 1.
Mockups (#30)	UI mockups of the dashboard and key screens.
Linter and formatter (#17)	Linters, formatters and pre-commit hooks.
CI pipeline (#18)	CI runs on every push and pull request. See Testing Plan and Continuous Integration.
Containerization (#19)	Run the application with Docker Compose.
Logging and error handling (#20)	Central logging and error handling foundation.
Test framework (#21)	Test framework, mocking and coverage tooling.

Tickets

Ticket	Title	Type	Status
#15	Select tech stack and justify frameworks and libraries	Spike	Open
#17	Configure linters, formatters and pre-commit hooks	Task	Open
#18	Set up CI pipeline on every push and pull request	Task	Open
#19	Containerize the application with Docker Compose	Task	Done
#20	Add central logging and error handling foundation	Task	Open
#21	Set up test framework, mocking and coverage tooling	Task	Open
#28	Create the architecture and layer diagram	Documentation	Open
#29	Create the domain model diagram	Documentation	Open
#30	Design UI mockups	Documentation	Open
#31	Write personas and the full user story backlog	Documentation	Open
#32	Write the problem statement and risk register	Documentation	Open

Overall summary

Velocity and contractor estimate

• Planned vs. done:
• What slipped:
• Done early:
• Contractor estimate for this iteration:

Retrospective

• What went well:
• What went wrong:
• Improvements:

Breakdown by individual

Member	Contributions (issues / PRs / commits)
Mohamad Addasi (@Moe1177)	#29 Create the domain model diagram: ER diagram of data model v1 (tenant, source, sync run, raw record, source record, organization, organization link, match candidate, record change) with relationships and cardinalities, showing tenancy, provenance, versioning, match outcomes and changes between sync runs. Wrote the explanation, glossary and the open questions for #25, and committed the Mermaid source. Published in Overall Architecture and Class Diagrams.
Hendrik Tebeng (@everythingzit) · 40282196	#26 Identifier normalization: clean organization/person names, websites, LinkedIn, emails and phones into one standard form so French and English variants of the same entity can be matched later. Implemented the module and unit tests; documented the business rules and approved libraries on Beyond-CRUD Flows (see also Infrastructure and Tools).