STAR WARS LEARNING DEMONSTRATION DATA
Prepared: 18 October 2026

Status and purpose
Applied locally to Dev_AlexForbes_HR on BRENDANDESKTOP. Two applications inside
one rollback rehearsal passed, followed by two idempotent applications committed
in one transaction and independent verification. This package adds fictional
Learning demonstration records for the four explicitly mapped Star Wars accounts.
It does not deploy or restyle dashboards. Dashboard/release changes are separate.

Owned business records
                           Credentials  Goals  Evidence  Milestones  Total
Leia                                40     36        32          24    132
Luke                                24     20        20          16     80
Ahsoka                              32     28        28          20    108
Obi-Wan                             28     24        24          20     96
Total                              124    108       104          80    416

Also added: 12 inactive manual demonstration credential definitions, 8 inactive
private demonstration milestone definitions and 3 missing employee learners.
Total: 439 owned business/configuration rows plus 439 ownership-registry entries.
Leia's pre-existing learner and all her existing records were retained.

Identity and ownership
CharacterMap.json is copied from the accepted Task demo mapping. Employee and
user identities resolve uniquely by company/employee number plus the fictional
first name/surname and active status. No employee or user ID is embedded in the
data SQL. The native analytics test resolves Leia as its actor (1549 locally).
The three reviewed competencies resolve by natural factor/element code and
description: Communication, Problem Solving and Teamwork. No shared competency,
level, job, position or requirement is created or changed.

Stable source keys start SW-LEARN-V1:, definition codes start SWLEARN-, and GUIDs
derive from the stable SW-LEARNING-DEMO-V1 namespace. The sidecar table
dbo.__Codex_StarWarsLearningSeed registers each newly inserted identity. Replay
preserves existing rows and IDs. Reserved unregistered collisions fail rather
than overwrite data. The first registered base date and mapping remain fixed.

Demonstration semantics
All new credential definitions are MANUAL, inactive and explicitly labelled DEMO
and simulation only. They represent no qualification, licence, training
certification, verified assessment or legally meaningful credential. No printable
certificate/template, previous-award relationship or course completion is issued.

The existing learner-reminder flag is enabled. Therefore every seeded credential
EXPIRES_ON is deliberately NULL. Existing reminder settings remain unchanged and
the seeded awards cannot enter the native expiry-reminder due set. Recorded states
include VALID, PENDING, REVOKED, SUSPENDED and SUPERSEDED. Native current risk is
source-authoritative; the two existing expired awards remain visible and unchanged.
No fictitious expiring/expired award is manufactured to fill a chart.

Goals are clearly fictional PERSONAL practice goals, using native ACTIVE, PAUSED,
ACHIEVED and CANCELLED statuses. They set no target job/position/company and do
not alter shared requirements. Synthetic manual evidence spans existing native
competencies and levels 1-3, with valid/pending/expired/revoked/rejected examples.
It contains no files and claims no approval. Achievement awards use native DEMO
classification and private inactive definitions; stored points are demonstration
points, not a real performance assessment. Some examples are explicitly revoked.

Dates span May-October 2026, anchored on 18 October 2026. Native dashboard cohort
rules are retained: issued date for credential awards, created date for goals,
evidence date for evidence, award date for achievements. Current risk/gaps remain
current source evidence. The selected 6 September-7 October preview has 25 owned
credential rows: Leia 8, Luke 7, Ahsoka 5, Obi-Wan 5. No dashboard filter is changed.

The native competency-gap view returns zero matching gaps for this cohort. This
is retained honestly; no job/position requirements are fabricated. Existing
development plans remain available; no legacy development-plan rows are seeded.

Boundaries
The package does not write employees, users, groups, memberships, access grants,
settings, assignments, content, schedules, certificates, files, events,
notifications, Mail Bot queues, workflows or shared requirements. No trigger is
disabled or changed. No native save/finalize routine that creates events is called.
The only schema addition is the ownership registry. New learners receive no copied
contact address; existing learners are preserved. Normal subsequent native UI
housekeeping can refresh learner metadata, as described below.

Files and execution
Four SQL files run in this exact order through Invoke-StarWarsLearningSeed.ps1:
000 - Preflight - Star Wars Learning Demo.sql
001 - Table - __Codex_StarWarsLearningSeed.sql
900 - Data - Star Wars Learning Demo.sql
999 - Verification - Star Wars Learning Demo.sql

The runner explicitly selects those SQL filenames. It never executes every file
in the folder. It reads the configured local HR connection when no explicit
connection is supplied; no connection string or credential is included here.
SQL requires the existing native Learning 2.0 schema and enabled Credentials,
Growth and Gamification features, plus SQL Server 2016 compatibility level 130+.
Only the development target below was validated. CharacterMap and reviewed
competency keys require review before reuse against another demo database.
The exact expected 439-row bundle assumes Leia already has her original learner
and the other three mapped accounts have no learner before the first apply.

From this extracted folder, run in PowerShell:

.\Invoke-StarWarsLearningSeed.ps1 -Mode Preflight -ExpectedDatabase Dev_AlexForbes_HR -ExpectedMachine BRENDANDESKTOP -DemoAcknowledged -BaseDate 2026-10-18 -ResultPath .\Preflight.json

.\Invoke-StarWarsLearningSeed.ps1 -Mode Rehearsal -ExpectedDatabase Dev_AlexForbes_HR -ExpectedMachine BRENDANDESKTOP -DemoAcknowledged -BaseDate 2026-10-18 -ResultPath .\Rehearsal.json

.\Invoke-StarWarsLearningSeed.ps1 -Mode Apply -ExpectedDatabase Dev_AlexForbes_HR -ExpectedMachine BRENDANDESKTOP -DemoAcknowledged -BaseDate 2026-10-18 -ResultPath .\Applied.json

.\Invoke-StarWarsLearningSeed.ps1 -Mode Verify -ExpectedDatabase Dev_AlexForbes_HR -ExpectedMachine BRENDANDESKTOP -DemoAcknowledged -BaseDate 2026-10-18 -BaselinePath .\Applied.json -ResultPath .\Verified.json

Rehearsal applies twice and rolls back. Apply applies twice and commits only if
owned identities/content remain identical on replay and every protected hash is
unchanged before/after and after the transaction. Any failure rolls back the
transaction. Identity gaps caused by rolled-back rehearsal are normal; no user or
employee key is generated or remapped. Preflight and Verify do not write permanent
tables. No automatic cleanup/delete is supplied: review registered IDs and native
relationships before removing demo records; preserve all original learners/data.

Verification evidence
All four scripts passed SQL Server 2016 ScriptDom parsing and identifier-bracketing
review. Real native constraints were enforced throughout rehearsal and apply.
Foreign keys, checks and unique constraints were inspected; all target source
tables had no enabled mutation triggers. Enabled triggers elsewhere were retained.

Twenty-five exact protected snapshots matched during rehearsal and committed
apply: non-owned rows of all seven touched Learning tables; users/employees;
groups/memberships; settings; Portal/Report access; native events/notifications;
certificates; Mail Bot queue/checklist; competencies/levels/job-position
requirements; all trigger state/definitions; and Learning SQL definitions.
The second application changed no owned data or registry identity.

All four native employee dashboards read the inactive demonstration definitions
correctly. All 61 native Growth widget/report commands passed for the authorised
Leia actor. Full-period owned report cohorts reconcile exactly after native
exclusions: Leia 40 credentials/30 goals/32 evidence/22 milestones; Luke
24/17/20/15; Ahsoka 32/24/28/18; Obi-Wan 28/20/24/18. Cancelled goals and revoked
milestones remain stored but do not enter those native analytic counts.

Actual full-cohort native KPIs for 20 May-18 October 2026, including preserved rows:
127 credential awards; 4 employees; 2 at risk/expired; 0 expiring/in grace;
94 goals; 56 active; 19 overdue; 107 evidence; 23 valid; 5 development plans;
4 open development plans; 0 current gaps; 80 non-revoked milestones; 2,345 points.
The credential grid previews 100 rows and its matching report returns all 127.
The evidence grid previews 100 rows and its matching report returns all 107.

Later legitimate activity
Applied.json preserves the strict, passing apply-time baseline. After commit,
the marketing agent opened Leia's native My Learning page; its normal
EnsureLearner routine refreshed the existing learner metadata. The primary agent
also increased default Learning KPI card heights through its separate function206
presentation refinement. Both later changes are acknowledged and retained.
Verified.json reports these later HRF_LEARNING_V2_LEARNER/LearningSql fingerprint
differences separately while confirming seed-owned invariants and native reads.
Verify reports unrelated later activity; it never overwrites it. Rehearsal/Apply
continue to enforce exact transactional isolation and rollback on differences.

Privacy and application integration
Evidence JSON contains aggregate counts, fictional aliases, identities/hashes and
checks only. No personal evidence narratives, contact values, private answers,
files or report workbooks are included. This package contains no application
source or release dashboard edits. Native dark screenshots are coordinated by the
primary/marketing agents from the existing implemented pages; no fabricated UI
or recoloured screenshot is supplied by this data package.
