Generated from corpus/packs/examples/cross-services-webapp-software.md. Do not edit by hand — run python scripts/generate-corpus-docs.py.

Example pack — Cross-line: Services web app → Software

Intent: Billable web app under a client engagement.
Lines: services (engagement) + software (delivery)
Active roles: role.engagement-manager then role.engineering-lead / role.implementer

Classification

Field	Value
services.sku	sku.dev-web-apps
services.engagement	eng.software
services.privacy	privacy.client-local
software.estate	usually private / not public Lab
software.app-kind	web-app
software.brand	brand.client
software.host	ask (konstant vs vercel); no public Lab catalog unless agreed

Plan

1. Services: win engagement; bind privacy + client folder.
2. Handoff handoff.services-code-to-software with engagement binding on the GitHub issue.
3. Software Frame/Design/Implement under client constraints.
4. Deploy only to agreed host; no hectorsanchez.eu/lab catalog unless craft showcase approved.
5. Deliverables land in client deliverables/; invoice on Services track.

Units

• services catalog + privacy
• software delivery inventories + standards secrets/github-first
• org handoffs.yml

Prohibited

• Publishing client code to public Lab by default
• Skipping Services privacy rules because “it’s software”