ITC-WP-0004 - Small SaaS Profile Proof

Goal

Create the first practical profile proof: a small SaaS system profile that uses the kernel, models, and standards without waiting for the larger CARING benchmark.

Intent

The first proof should show that InfoTechCanon can guide a real implementation shape: service ownership, users, tenants, access, data, runtime, deployment, governance, observability, and work tracking.

Tasks

T01 - Profile definition

id: ITC-WP-0004-T01
status: planned
priority: high

Create infospace/profiles/small-saas/.
Define scope, assumptions, required standards, and conformance level.
Declare which model concepts are required, optional, or out of scope.

T02 - Example artifacts

id: ITC-WP-0004-T02
status: planned
priority: high

Add example service, system, tenant, user, team, dataset, deployment, task, policy, control, evidence, and incident artifacts.
Keep examples small but connected.
Add relationships suitable for graph export.

T03 - Validation rules

id: ITC-WP-0004-T03
status: planned
priority: high

Define required fields and links for small SaaS artifacts.
Validate service ownership.
Validate tenant and namespace separation claims.
Validate user-management and access-control traces.
Validate evidence links for governance claims.

T04 - Report and demo commands

id: ITC-WP-0004-T04
status: planned
priority: medium

Add a profile report under infospace/reports/.
Add CLI/API inspection examples.
Produce a graph view of the small SaaS proof.

Acceptance

The small SaaS profile is the first executable proof of the canon.
Profile artifacts validate through the service surface.
The proof produces useful graph and JSON outputs.
The result is suitable as the baseline for user-engine and railiance-fabric evaluation.

2.1 KiB Raw Blame History