Phase A — Architecture Vision

1. Statement of architecture work

Problem. The current repository is a skeleton that does not build (one package is a lone tsconfig.json, another is referenced but absent) and still carries naming from a previous employer. It cannot be published as it is.

Scope. Turn it into a public, portfolio-grade SharePoint Framework monorepo under Orpheus Systems that:

1. builds from a clean clone with nothing but Podman installed;
2. demonstrates all four SPFx extension types plus a real web part;
3. solves one concrete business problem end to end: tracking a contractor's on-site / off-site days against a procurement contract and printing the signed timesheet.

Desired outcomes (design §2, goals):

Out of scope for this iteration (design §2, non-goals): SharePoint item-level permissions; automatic holiday population by an agent; approval workflow / e-signature; SharePoint on-premises; multi-language UI (strings structure kept so it can be added).

Anti-goals (would make the result a failure even if it works): anything that identifies a previous employer or a real client; builds that only work on the author's machine; fake-looking demo data.

2. Stakeholders

⚠️ Open: The design does not say who the first real tenant users are or how many; the SharePoint Online tenant is described only as "available for verification".

3. Business drivers

• Make the repository public and worth showing (portfolio value for Orpheus Systems).
• Replace a non-building skeleton with a product that builds reproducibly.
• Solve a real, recurring need: counting a consultant's on-site and off-site days per contract, including bridge contracts that overlap, and producing the timesheet the approving organisation signs.

4. Constraints (design §3)

⚠️ Open: The org/repo and npm-scope reading of the namespace "orpheussystems.sharepoint" is marked "confirm" in the design (§3, §11).

⚠️ Open: Timeline and budget are not stated in the design.

5. System context

C4Context
  title System context — Orpheus contract calendar suite
  Person(contractor, "Contractor", "Marks on-site / off-site days on own contracts; prints timesheet")
  Person(manager, "Contract manager", "Manages a contract or is in Orpheus Contract Managers; creates contracts, edits managed ones; generates timesheet")
  Person(admin, "Site admin", "Site collection admin or Owners member; edits any contract; maintains Holidays; configures web part")
  System(suite, "Orpheus SPFx suite", "Application customizer, calendar web part, field customizer, form customizer, shared packages")
  System_Ext(spo, "SharePoint Online site", "Contracts, CalendarEntries and Holidays lists; modern page ContractCalendar.aspx")
  System_Ext(browser, "User's browser", "Runs the SPFx bundles; generates and downloads the PDF")
  System_Ext(prov, "Provisioning (PnP PowerShell 3 on PowerShell 7.4, host)", "Provision-OrpheusSite.ps1 -InstallSolutions with OrpheusSolutions.psm1: lists, App Catalog install, header, bindings, group, page")
  Rel(contractor, suite, "Uses")
  Rel(manager, suite, "Uses")
  Rel(admin, suite, "Uses and configures")
  Rel(suite, spo, "Reads/writes lists via PnPjs v4")
  Rel(suite, browser, "Renders UI, produces Timesheet_<ContractCode>_<from>_<to>.pdf")
  Rel(prov, spo, "Creates content types and lists; installs the four .sppkg in the site collection App Catalog; registers the header; binds customizers; creates Orpheus Contract Managers and ContractCalendar.aspx")

6. Success measures

7. Initial risk register

8. Assumptions

📝 Assumption: A single SharePoint Online site hosts all three lists and the calendar page; multi-site deployment is not addressed in the design.

📝 Assumption: Hours per day default to 8 and half days print as 4.00; non-default HoursPerDay values print HoursPerDay and HoursPerDay / 2. The design states the default and the printed values but not the general rule.