Exercise,Module,Journey,Environment,Profiles,Record / version reference,Preparation,Open,Actions,Expected evidence,Engineering evidence,Actual result,Result,Evidence reference,Defect / follow-up,Retest result
KRN-CORE-01,Kernel Core,Register an organization without duplicating its identity,,,,Registered / display name = Example Services Training; Kind = ORGANISATION; Email / telephone / web = office@example.test / approved training phone / https://example.test; Address = 10 Example Road; Training Town; TT10 1AA,Core → Party directory → Onboard organization,"1. Search Party directory for the organization name and inspect likely matches. 2. Open Onboard organization and complete the organization and required contact/address steps. 3. Check the subtype, spelling and contact ownership before Create organization. 4. Return to Party directory and open the returned organization. 5. Open Organizations and the relevant contact/address association.",Show the saved organization reference and its associated contact/address records. Explain that no IAM assignment or tenant activation was created.,KRN-E-CORE,,Awaiting client execution,,,
KRN-CORE-02,Kernel Core,Register a person and maintain structured names,,,,Given / family name = Alex / Example; Display name = Alex Example; Kind = PERSON; Email = alex@example.test,Core → Party directory → Onboard person; People; Person names,"1. Search People and Party directory for the person. 2. Open Onboard person, enter the structured names and review optional contact/address details. 3. Create the person once and retain the returned reference. 4. Open Person names and Display names for that party. 5. For a correction, open the existing name action, check the latest version and save the authorized change.","Show two distinct party references, the structured person name and the absence of any automatic account grant.",KRN-E-CORE,,Awaiting client execution,,,
KRN-CORE-03,Kernel Core,Add contacts and addresses to the correct party,,,,Owning party = Alex Example’s returned reference; Contact kind / value = EMAIL / alex.notifications@example.test; Purpose = Select the offered notification/contact purpose; Address = 12 Example Road; Training Town; TT10 1AB,Core → Add contacts or address; Contact assignments; Address assignments,"1. Open the party and inspect current contact/address assignments. 2. Use Add contacts or address with the intended party reference. 3. Enter the new contact or address and its applicable purpose. 4. Save and inspect Email contacts, Telephone contacts or Web contacts as appropriate. 5. Inspect Contact assignments / Address assignments and preferred indicators.","Show destination, assignment, owning party and purpose as separate but linked facts.",KRN-E-CORE,,Awaiting client execution,,,
KRN-CORE-04,Kernel Core,Build an organization hierarchy and classification,,,,Parent organization = Example Services Training; Child organization = Example Regional Office; Relationship type = Approved parent/subsidiary type from the relationship catalog; Classification = Approved training classification,Core → Relationship catalogs; Define relationship type; Link organizations; Organization hierarchy; Classification workspace,"1. Inspect the relationship catalog before creating a link. 2. Open Link organizations and select the source and target in the correct direction. 3. Enter the applicable period and reason, then save through the offered governed action. 4. Open Organization hierarchy and follow the link from each relevant node. 5. Assign a controlled classification separately in Classification workspace.","Show the hierarchy direction, the classification and their independent references.",KRN-E-CORE,,Awaiting client execution,,,
KRN-CORE-05,Kernel Core,Maintain geography and associate an address,,,,Levels = Existing Country → State → Locality levels; Locality code / name = TRAINING_TOWN / Training Town; Parent = The selected eligible State place; Address = Alex Example’s saved training address,Core → Define geography level; Define place; Place hierarchy; Address geography workspace,1. Inspect existing levels and places to avoid duplicates. 2. Define a missing eligible level or place through the offered form. 3. Open Place hierarchy and inspect the full parent path. 4. Use Assign address geography for the saved address. 5. Read back the address in Address geography workspace.,"Show the place path and address association, not just a matching typed locality.",KRN-E-CORE,,Awaiting client execution,,,
KRN-CORE-06,Kernel Core,Maintain reference masters with their business meaning,,,,Master family = Contact Kind; Code / name = TRAINING_DESK / Training desk contact; Description = Contact destination used by the training service desk; Active = Yes initially; later propose inactivation,Core → Reference Masters → selected master,1. Open the relevant master and search its code and meaning. 2. Open the current record or permitted create action and complete its declared fields. 3. Review active state and dependency implications before saving/submitting. 4. Complete any required review on the owning record. 5. Inspect a consumer lookup and then the original history.,"Show the correct master family, saved state and a consumer lookup containing the eligible value.",KRN-E-CORE,,Awaiting client execution,,,
KRN-CORE-07,Kernel Core,Define and publish state transitions and reason policy,,,,Dimension / consumer = Training review lifecycle / selected training consumer; States = DRAFT initial; REVIEW; APPROVED terminal; Transitions = DRAFT → REVIEW on SUBMIT; REVIEW → APPROVED on APPROVE; Reason = VERIFIED_REVIEW; narrative required for APPROVE,Core → State Model Designer; Reason Policy Designer; Model publications,"1. Define the required states and transitions in the selected dimension. 2. Define reason values and applicability, including required narrative. 3. Propose model publication for the chosen consumer. 4. Have the eligible independent reviewer compare and decide that proposal. 5. Use Check a published transition with a valid action/reason combination. 6. Repeat the non-mutating check with a disallowed transition or missing required narrative.",Show one allowed and one rejected evaluation plus the immutable published reference.,KRN-E-CORE,,Awaiting client execution,,,
KRN-CORE-08,Kernel Core,Inspect party assurance before using the organization downstream,,,,Party = Example Services Training; Assurance evidence = The offered evidence/reference fields with a training evidence reference; Status / reason = The offered verification result and attributable reason,Core → Party assurance,1. Open Party assurance for Example Services Training. 2. Inspect each offered assurance fact and its source. 3. Use the authorized evidence/review action with the training reference and reason. 4. Reopen the party and then the Tenant onboarding selector.,"Show the party reference, assurance source, recorded outcome and the unchanged account/tenant boundaries.",KRN-E-CORE,,Awaiting client execution,,,
KRN-TENANT-01,Tenant Engine,"Create, save and review a tenant onboarding request",,,,Tenant code / name = TRAINING_TENANT / Example Services Training Tenant; Type = An offered eligible training/operating-unit type; Organization = Example Services Training; Contact / email = Training Owner / owner@example.test; Reason / evidence = Training onboarding rehearsal / prepared organization evidence reference,Tenant Engine → Tenant onboarding; Onboarding requests; Tenant registration review,"1. Search Onboarding requests before creating another intake. 2. Enter the tenant, organization, contact and readiness fields. Save the draft. 3. Leave the form and reopen the request. 4. Submit the exact request for independent review. 5. The reviewer checks the organization, type and evidence and records a reasoned decision. 6. Open Tenant onboarding cases and locate the corresponding case.","Show draft resumption, independent decision and the case reference.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-02,Tenant Engine,Provision runtime identity and bind the organization,,,,Approved intake = TRAINING_TENANT’s exact request; Runtime identity = Server-issued tenant reference; Organization binding = Example Services Training’s reference; Execution reason = Provision reviewed training tenant,Tenant Engine → Tenant runtime provisioning; Tenant runtime registry; Tenant organization binding,1. Open the approved intake in Tenant runtime provisioning. 2. Inspect prior execution/readback before starting another attempt. 3. Run the supported provisioning action. 4. Open Tenant runtime registry for that reference. 5. Confirm Tenant organization binding and reopen the onboarding case.,"Show request ID, case ID, tenant ID and organization ID with their separate meanings.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-03,Tenant Engine,Capture and independently review business identity evidence,,,,Legal name / registration number = Example Services Training / TRAIN-REG-001; Authority / jurisdiction = The approved training registry and jurisdiction lookups; Registry URL = https://example.test/registry/TRAIN-REG-001; Validity / evidence = A future permitted validity bound / admitted custody version,Tenant Engine → Capture identity evidence; Identity evidence review; Check business identity,"1. Select the intended runtime tenant in Capture identity evidence. 2. Complete legal, registry, jurisdiction and validity fields and save/submit. 3. If a supporting file is needed, upload it through Document custody and inspect processing/scanning. 4. The reviewer compares the evidence and records the independent decision. 5. Run Check business identity and return to the owner-step/case view.","Show evidence scope, review outcome, validity and the resulting identity check.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-04,Tenant Engine,Publish typed tenant settings and restore a version,,,,Setting = DEFAULT_TIME_ZONE; Version 1 value = UTC; Version 2 value = Asia/Kolkata; Second setting = DEFAULT_LOCALE = en-IN; Reason = Training configuration and reviewed restoration,Tenant Engine → Tenant configuration review; Tenant configuration versions; Effective tenant configuration,"1. Inspect Effective tenant configuration before editing. 2. Draft the selected setting for the target tenant with a typed value and reason. 3. Submit and have the eligible reviewer compare current and proposed values. 4. Publish the approved configuration and open Tenant configuration versions. 5. Reopen Effective tenant configuration and verify the new value. 6. For an approved restoration exercise, use Restore configuration version with the retained eligible version.","Show draft/current separation, decision, publication and effective readback.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-05,Tenant Engine,Review a plan and bind a tenant subscription,,,,Plan = TRAINING_STANDARD / Training standard plan; Tenant = TRAINING_TENANT’s runtime reference; Term / entitlement bounds = The offered effective period within the approved plan term; Evidence / reason = Prepared training subscription authority / training binding,Tenant Engine → Commercial proposal review; Commercial subscriptions; Check commercial subscription,"1. Inspect the existing commercial plans and select or propose the intended version. 2. Complete commercial plan review through the offered proposal decision. 3. Set up the tenant subscription against that exact version and complete its review. 4. Inspect Commercial subscriptions for state and period. 5. Run Check commercial subscription and inspect the onboarding owner step. 6. If cancellation is required, use Request subscription cancellation and review its effect before further operations.","Show the plan version, separate tenant subscription and successful or deliberately blocked owner check.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-06,Tenant Engine,"Claim, verify, activate and revoke a tenant domain",,,,Domain = A DNS name in a training zone controlled by the team; Tenant = TRAINING_TENANT; Challenge = The exact challenge name/value returned by the domain service; Reason = Verify training domain ownership,Tenant Engine → Tenant domains → contextual domain actions,"1. Inspect existing domain claims for the intended tenant. 2. Claim the hostname and complete the required review. 3. Place the exact current challenge in controlled DNS and use Check DNS ownership. 4. If needed, renew the challenge and publish its new value before verifying again. 5. Use Activate verified domain only when its prerequisites are satisfied. 6. For withdrawal, use Revoke domain and inspect the resulting state.","Show current challenge, verification, activation state and their separate references.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-07,Tenant Engine,Resolve owner-step blockers and publish signed tenant truth,,,,"Onboarding case = The case returned for TRAINING_TENANT; Owner checks = Organization, identity, configuration, commercial and applicable domain/support/residency checks; Truth snapshot = Returned signed publication and digest; Reason = Publish reviewed training readiness",Tenant Engine → Onboarding owner steps; Tenant onboarding cases; Tenant truth publications,"1. Open the saved onboarding case and inspect each owner step. 2. Follow the owning action, resolve its input and rerun its check. 3. Repeat for all required checks and inspect their freshness. 4. Publish signed Tenant truth through the permitted action. 5. Open that publication and retain its version/reference for TCP.","Show a blocker, its owner correction and the signed truth consumed by the next module.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-08,Tenant Engine,"Maintain tenant relationships, branding, suspension and exit proposals",,,,"Tenant = TRAINING_TENANT; Change family = Relationship, branding, suspension or exit proposal; Reason = Training change to the selected family; Evidence = Current owner references required by that family",Tenant Engine → Tenant operations; Tenant relationships; Published tenant branding; Tenant change review,"1. Inspect the current tenant and relevant relationship/branding state. 2. Open the contextual change proposal matching the requirement. 3. Save and submit the proposal with a clear reason. 4. The reviewer decides the exact proposal in its owning change context. 5. Read back relationships or branding preview and inspect history. 6. For exit, retain the accepted request and continue governed closure in TCP.","Show before/after, decision and the boundary between an accepted request and executed lifecycle change.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-09,Tenant Engine,Create and review the tenant type used by the intake,,,,Type code / name = TRAINING_OPERATING_UNIT / Training operating unit; Reason = Classify the training tenant consistently,Tenant Engine → Tenant types → owning type record,1. Search for the required operating-unit type. 2. Create TRAINING_OPERATING_UNIT with its business name and reason. 3. Complete the type’s offered review on that record. 4. Reopen Tenant onboarding and select the eligible type.,"Show the type definition, its decision and the intake’s selected reference.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TENANT-10,Tenant Engine,Renew domain evidence without losing the previous claim history,,,,Existing claim = The training domain’s current claim and version; Renewal challenge = Fresh returned DNS challenge; Reason = Renew training domain ownership,Tenant Engine → Tenant domains → contextual domain actions,1. Open the existing domain and read its current evidence/expiry. 2. Run the authorized renewal action and retain its returned challenge. 3. Have the training DNS owner publish the required value and verify it. 4. Reopen the onboarding owner checks and refresh domain readiness.,"Show the old and new domain evidence, current challenge result and refreshed owner check.",KRN-E-TENANT,,Awaiting client execution,,,
KRN-TCP-01,Tenant Control Plane,"Request, review and register an environment",,,,"Tenant = TRAINING_TENANT; Environment code / name = TRAINING_PREUAT / Training Pre-UAT; Target / topology = The offered approved target, initially a bounded shared training target; Reason = Register a reviewed training environment",Tenant Control Plane → Environment control,"1. Inspect Environment control for existing environments of the tenant. 2. Use Request an environment and complete the tenant, type, code and purpose. 3. Submit the request and have an independent eligible reviewer decide it. 4. Use Register approved environment for that accepted request. 5. Reopen Environment control and inspect its current readiness.","Show the request, approval and registered environment reference.",KRN-E-TCP,,Awaiting client execution,,,
KRN-TCP-02,Tenant Control Plane,Plan deployment and inspect provision/recovery,,,,Environment = TRAINING_PREUAT; Deployment template = An offered approved template and exact version; Configuration = Current effective environment/tenant publications; Reason = Deploy reviewed training environment,Tenant Control Plane → Deployment and recovery,"1. Open the environment’s Deployment and recovery workspace. 2. Create the supported local/shared deployment plan and review its target. 3. Submit and obtain the required independent decision. 4. Use Provision or recover once and inspect the response. 5. Read back the environment/deployment status after any interrupted response. 6. If recovery is offered, use the current failed attempt and reason.","Show approved plan, exact target, execution result and any recovery lineage.",KRN-E-TCP,,Awaiting client execution,,,
KRN-TCP-03,Tenant Control Plane,Promote and restore environment configuration,,,,Source setting = DEFAULT_TIME_ZONE = UTC; Target environment = TRAINING_PREUAT; Replacement = Asia/Kolkata if offered by the target definition; Restore selection = The previous permitted published value,Tenant Control Plane → Environment configuration,"1. Inspect the target’s current configuration version. 2. Open Promote environment configuration and select the target and source. 3. Choose the intended version, explain the change and submit. 4. The reviewer decides the exact proposal, then the authorized action publishes it. 5. Read back effective configuration and retain the earlier publication. 6. For a restoration exercise, use Restore environment version with an eligible prior version and reason.","Show source snapshot, target adoption and restoration evidence.",KRN-E-TCP,,Awaiting client execution,,,
KRN-TCP-04,Tenant Control Plane,Bind residency and support policy,,,,Residency = The approved target location / region offered by the platform; Support tier = ENTERPRISE when offered by the training contract; Support queue = The approved configured training support queue; Reason = Bind support and residency for training environment,Tenant Control Plane → Residency and support policies; Effective residency and support,1. Inspect existing effective residency and support for the tenant. 2. Use Bind platform residency or Define plan support as appropriate. 3. Submit the proposal with its supporting reason. 4. The reviewer compares the binding and decides it. 5. Open Effective residency and support and inspect the result.,"Show the policy decision and effective binding, including its tenant scope.",KRN-E-TCP,,Awaiting client execution,,,
KRN-TCP-05,Tenant Control Plane,"Grant, expire and revoke module entitlement",,,,Tenant / module = TRAINING_TENANT / an offered Kernel module entitlement; Grant value = true; Expiry = A future bound within the approved plan term; Reason = Allow the training module within the approved term,Tenant Control Plane → Entitlement approvals; Current module grants,"1. Inspect Current module grants for the intended tenant. 2. Request the selected module entitlement with an explicit access choice and expiry. 3. Complete the eligible independent decision on the entitlement record. 4. Read back Current module grants and compare module, access and period. 5. Test access with an otherwise eligible IAM profile. 6. For withdrawal, request entitlement revocation and review it.",Show the exact module grant and an authorized user journey; explain why a tenant grant is not a user role.,KRN-E-TCP,,Awaiting client execution,,,
KRN-TCP-06,Tenant Control Plane,Activate or restore a tenant using current readiness,,,,Tenant = TRAINING_TENANT; Truth / owner evidence = Current eligible tenant-truth snapshot and required owner results; Action = Activate or restore as offered for the current state; Reason = Activate the reviewed training tenant,Tenant Control Plane → Activation and restoration,"1. Open the lifecycle workspace and inspect its readiness checks. 2. Resolve blockers in Tenant Engine, environment configuration, policy or entitlements. 3. Request activation or restoration for the eligible environment. 4. The reviewer decides the current version. 5. Use Activate or restore tenant and retain the returned receipt. 6. Reopen the tenant/environment and inspect current state.","Show readiness, proposal decision, execution receipt and effective tenant state.",KRN-E-TCP,,Awaiting client execution,,,
KRN-TCP-07,Tenant Control Plane,Close a tenant exit with evidence retained,,,,"Tenant = A disposable suspended training tenant; Exit evidence = Required custody, commercial and owner closure references; Effective closure = The permitted intended closure bound; Reason = Close the isolated training tenant",Tenant Control Plane → Governed exit closure,1. Open the accepted Tenant Engine exit request and follow the closure context. 2. Inspect outstanding dependencies before proposing closure. 3. Submit Request governed exit closure with its reason and evidence. 4. The eligible reviewer inspects the exact revision and completes Review and close tenant. 5. Read back tenant state and retained history.,"Show the accepted exit request, closure authority and preserved history.",KRN-E-TCP,,Awaiting client execution,,,
KRN-TCP-08,Tenant Control Plane,Suspend a training tenant and restore it from current evidence,,,,Tenant = The disposable active training tenant; Reason = Training suspension and controlled restoration; Evidence = Current lifecycle version and review reference,Tenant Control Plane → Activation and restoration,1. Inspect the active training tenant and affected users/jobs. 2. Submit suspension with the permitted reason and obtain the required review. 3. Inspect the owner application result and effective availability. 4. Refresh readiness and use the governed restoration action.,"Show proposed/approved/applied suspension separately, the current readiness check and the restoration receipt.",KRN-E-TCP,,Awaiting client execution,,,
KRN-AXIS-01,Axis,Open the owning screen and inspect its controls,,,,Screen search = Domains; Control example = Domain name; Record identity = Returned screen/control references,System Access → Experience Administration → Screens,"1. Search Screens for the intended business screen. 2. Select Open screen and inspect Screen details. 3. Select Fields / Controls. 4. Open a field or action and compare its stable identity and type. 5. Refresh, return to Screen details and use Back.","Show one owning screen, its details and its child controls through refresh and Back.",KRN-E-AXIS,,Awaiting client execution,,,
KRN-AXIS-02,Axis,Maintain the screen title and header help,,,,"Screen = Domains; Title = Training Domains; Header help = Create a domain, then explicitly link eligible profiles. Review changes on this record.; Reason = Clarify domain setup instructions",Screens → selected screen → Screen details,1. Open Screen details and read the current title/help. 2. Enter a precise replacement title or help text with a business reason. 3. Save/submit the supported presentation change. 4. The eligible reviewer compares before/after and decides on the same screen. 5. Reopen the rendered business screen and its question-mark help. 6. Inspect the owning record’s history.,"Show current/pending comparison, decision and the actual rendered tooltip.",KRN-E-AXIS,,Awaiting client execution,,,
KRN-AXIS-03,Axis,"Edit a control label, help and display format in context",,,,Owner / field = Domains / Domain name; Display label = Business domain name; Control help = Use a name that describes the business access scope.; Display format = TEXT where offered; Reason = Clarify the field for training users,Screens → selected screen → Fields / Controls → selected control,1. Open the control under its owning screen and inspect current presentation. 2. Edit label/help/format and enter the reason. 3. Submit the change and inspect Changes & Approvals on that record. 4. The reviewer approves or rejects the exact revision. 5. Reopen the consuming screen under the intended functional profile. 6. Repeat with a profile lacking update permission.,"Show the label in its owner workspace and rendered business context, plus one permission-restricted action.",KRN-E-AXIS,,Awaiting client execution,,,
KRN-AXIS-04,Axis,Create a source-bound screen and explain every setup field,,,,Screen code / name = custom-training-domains / Training Domain Directory; Description / header help = Training domain directory / Explain explicit profile links and independent review; Layout = Table; Navigation section / menu group = Training administration / Directories; Registered business source = IAM · Domains; Reason = Create the training domain directory,Screens → Create Screen → Screen Details,"1. Open Create Screen and enter unique code, name and purpose. 2. Choose Table for a directory or Record details for a selected-record view. 3. Set the navigation section and optional menu group deliberately. 4. Select an eligible registered business source. 5. Save Draft and reopen it before continuing. 6. Open Fields / Controls and then IAM Access Mapping.","Show the saved source, layout and sidebar location and explain their separate meanings.",KRN-E-AXIS,,Awaiting client execution,,,
KRN-AXIS-05,Axis,Add fields and map existing IAM permissions,,,,Control 1 = domain_name → source name; TEXT; wide; Control 2 = domain_code → source code; TEXT; normal; Navigation / page permissions = Existing eligible permissions offered for the Domains source; Control permissions = The selected allowed permission for each of the two fields,Selected authored screen → Fields / Controls; IAM Access Mapping,"1. Add the needed source fields to the saved screen. 2. Order the controls and provide labels/help. 3. Select the existing page/control permission references. 4. Inspect the proposed menu/screen bridge and selected permissions. 5. Save and preview as the intended author, then verify using the functional profile after publication.","Show control/source binding, permission reference and the separate effective role grant.",KRN-E-AXIS,,Awaiting client execution,,,
KRN-AXIS-06,Axis,"Preview, review, publish and revise without losing authority",,,,Definition = custom-training-domains current saved revision; Author preview = Preview exact saved fields and access mapping; Reviewer preview = Independent checker previews the same submitted revision; Reason = Publish the independently checked directory,Selected screen → Preview; Changes & Approvals; mapping context,"1. Save the draft and preview its source-bound presentation. 2. Submit through the screen’s supported action. 3. Where ownership confirmation is required, the eligible responsible-role owner completes that stage. 4. The eligible independent reviewer compares the exact current submission and decides. 5. Complete the permitted publication/activation action for the approved version. 6. For a later change, revise through a new proposal and repeat preview/review.","Show preview, on-record decision, effective rendering and a rejected/stale case.",KRN-E-AXIS,,Awaiting client execution,,,
KRN-AXIS-07,Axis,Retire a custom screen while retaining its definitions and review history,,,,Screen = Published custom-training-domains; Action / reason = Retire / End the training-only directory,Selected screen → Preview; Changes & Approvals; mapping context,1. Open the published training screen’s originating record. 2. Submit the supported retirement request and reason. 3. Have the eligible reviewer decide the same record. 4. Refresh dynamic navigation and test the old deep link with the ordinary profile.,"Show pending versus approved retirement, removed operational availability and retained history.",KRN-E-AXIS,,Awaiting client execution,,,
KRN-AXIS-08,Axis,Recover a mapping review invalidated by changed dependencies,,,,"Screen / control = Training Domain Directory / domain_name; Changed dependency = The selected permission, source or control revision; Reason = Refresh the exact mapping after dependency change",Axis → Permission Mappings; selected owning screen → changes,1. Open the owning screen’s saved mapping and its current dependencies. 2. Inspect the prepared dependency-change example and the invalidated review. 3. Resolve the intended current references and save the corrected successor. 4. Preview and complete independent review on the same owning record.,"Show the invalidated reference, corrected mapping and fresh review evidence.",KRN-E-AXIS,,Awaiting client execution,,,
KRN-TIMEVAULT-01,TimeVault,Create a Country with an explicit effective period,,,,Country code / name = ZZ / Training Country; Effective period = 1 January through 31 December of the selected training year; Reason = NEW_RECORD / Establish the training Country; Request identity = Returned submission reference,Core Masters → Country → Create,"1. Search Country by code and name before creating. 2. Enter the record values, effective period and business reason. 3. Select Preview dates and inspect the returned timeline. 4. If any input changes, preview again, then Submit for review. 5. The independent reviewer opens the same Country record and its change. 6. After approval, reopen the timeline and current list.","Show proposed period, independent decision and the distinction between approved and currently effective.",KRN-E-TIMEVAULT,,Awaiting client execution,,,
KRN-TIMEVAULT-02,TimeVault,Create a State within an eligible Country period,,,,State code / name = ST / Training State; Parent Country = Training Country’s saved business reference; Effective period = A period fully covered by approved adjacent Country segments; Reason = NEW_RECORD / Add the training State,Core Masters → State → Create,"1. Inspect the Country timeline and its approved period. 2. Open State creation and select that Country. 3. Enter State values and dates, then Preview dates. 4. Submit and have the independent reviewer decide the saved State request. 5. Read back State under the effective date view.","Show parent reference, child period and the approved State timeline.",KRN-E-TIMEVAULT,,Awaiting client execution,,,
KRN-TIMEVAULT-03,TimeVault,Correct an existing version without changing its identity,,,,Target = Current Training Country version and revision; Correction = Training Country Corrected; Period = The unchanged full selected period; Reason = The offered correction reason and explanatory narrative,Country or State → View record → Propose edit,"1. Open the record and inspect its current periods. 2. Use Propose edit and correct only the permitted non-key values. 3. Set dates deliberately and preview the treatment. 4. Submit the change and retain its request reference. 5. After decision, compare current and preserved versions.","Show fixed keys, pending/current separation and retained previous values.",KRN-E-TIMEVAULT,,Awaiting client execution,,,
KRN-TIMEVAULT-04,TimeVault,Slice and Dice a bounded correction and inspect all periods,,,,Original period = 1 January–31 December of the training year; Changed middle period = 1 June–31 August of that same year; Middle value = Training Country Summer; Reason = PERIOD_CHANGE / Correct the middle interval,Country or State → row actions → Slice and Dice,"1. Open a long enough approved segment and select Slice and Dice. 2. Set the correction to D1 through D2 and change the intended name/description. 3. Select Preview dates and inspect every segment. 4. Confirm there are no gaps or overlaps before submitting. 5. The reviewer compares the entire treatment and records the decision. 6. Query an effective date before, inside and after the correction.",Show all three effective-date results and the preserved original representation.,KRN-E-TIMEVAULT,,Awaiting client execution,,,
KRN-TIMEVAULT-05,TimeVault,"Approve, reject and recover a saved workflow handoff",,,,Pending request = The bounded Training Country change; Decision = Approve or reject with a meaningful reason; Workflow reference = Returned review instance/checkpoint,Country/State → selected record → Changes and review,"1. Open the pending change from the Country/State record. 2. Compare before/proposed values and every timeline segment. 3. Enter the decision and comments and submit once. 4. Read back the owning timeline and change history. 5. If a saved request lacks its workflow instance, the maker uses Send to Regulix. 6. After an interrupted decision, reload the current change before retrying.","Show an approval, a rejection and the saved-request recovery path.",KRN-E-TIMEVAULT,,Awaiting client execution,,,
KRN-TIMEVAULT-06,TimeVault,Use effective-on and recorded-as-of views correctly,,,,Record = Training Country ZZ; Effective on = 15 July of the selected training year; Recorded as of = Before versus after the bounded correction’s recorded time; Comparison = Training Country versus Training Country Summer,Country/State → Date views; record → Preserved versions,1. Open the corrected record and inspect the current approved timeline. 2. Set Effective on to a date before the bounded correction. 3. Set it inside and then after the correction. 4. Apply Recorded as of using a point before the correction was recorded. 5. Clear the chips and open Preserved versions.,Show the same identity under three business dates and two recorded-time views.,KRN-E-TIMEVAULT,,Awaiting client execution,,,
KRN-TIMEVAULT-07,TimeVault,Inactivate or remove a version from use,,,,"Target = Training State ST current approved version; First action = Inactivate version; Second action = Remove from use, where authorized; Reason / interval = The intended bounded withdrawal and explanation",Country/State → selected current period → More actions,1. Inspect current segments and dependent State coverage before withdrawing a Country. 2. Select Inactivate version or Remove from use for the intended period. 3. Preview dates and review the affected intervals. 4. Submit and obtain the eligible independent decision. 5. Read back the effective list and preserved versions.,Show default availability and retained history after a permitted withdrawal.,KRN-E-TIMEVAULT,,Awaiting client execution,,,
KRN-VISTA-01,Vista,Register a bounded source connection and discover fields,,,,Name / code = Training Case Records / TRAINING_CASE_CONNECTION; Row path = data.records when the response is {data:{records:[...]}}; Authentication = The offered public or private credential-reference mode appropriate to the approved endpoint; Limits = 50 rows; 10 seconds; Scope = Tenant-field matching for tenant data; public only for genuinely public synthetic data,Vista → Sources & datasets → Connections → New connection,"1. Inspect existing connections before creating another. 2. Save the connection draft with endpoint, authentication reference, row path and limits. 3. Run Test & discover; if queued, Check test result until it finishes. 4. Inspect the returned contract and sample rows against the endpoint. 5. Submit, obtain the independent current test/review and publish.","Show connection revision, private reference type, READY discovery and published contract.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-02,Vista,Define the source and publish a selected dataset,,,,Source = Training Cases from the reviewed connection; Dataset name / code = Training Case Summary / TRAINING_CASE_SUMMARY; Selected fields = record_id TEXT; name TEXT; status TEXT; amount NUMBER; Prepared rows = CASE1001 OPEN 1000; CASE1002 OPEN 500; CASE1003 CLOSED 500; Preview limit = 50,Vista → Source Definitions; Datasets → New dataset,"1. Create the source definition against the eligible connection/registered source. 2. Save/review/publish the source through its offered lifecycle. 3. Create the dataset, select the intended source(s) and explicit output fields. 4. Preview and compare 3 training rows, total 2000 and OPEN total 1500. 5. Save the dataset and have the independent reviewer preview the same saved model. 6. Publish and retain the dataset version/reference.",Show connection → named source → dataset as three distinct controlled records.,KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-03,Vista,"Model joins, calculations and filters without changing the grain silently",,,,"Source main = Claims: (id 1, member 10, amount 12.5), (2,20,8), (3,null,4); Source lookup = Members: (id 10, name ""  alice  ""), plus a null-id row; Join = LEFT: main.member = lookup.id; Calculated outputs = claim_id; member_name = upper(trim(name)) with UNKNOWN fallback; double_amount = amount × 2; Safe ratio = amount / 0","Dataset → Dataset structure → Model sources, joins and calculations","1. Choose a primary source and add the required secondary source. 2. Select compatible keys and the join type. 3. Select named outputs and add a calculation with the offered expression controls. 4. Preview matched, unmatched, empty and zero-value cases. 5. Compare parent count before and after a one-to-many join. 6. Save, independently preview/review and publish the exact model.","Show join kind, preview cardinality and one calculation with its expected values.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-04,Vista,"Build a report with meaningful table, summary and chart blocks",,,,"Dataset = Published Training Case Summary; Report name / code = Training Case Operations / TRAINING_CASE_OPERATIONS; Table = record_id, name, status, amount; Summary / grouping = Count record_id; group by status; sum amount; Layout = A4 portrait; body table; summary and bar/column comparison",Vista → Create Report → source/dataset selection → report details → Report Studio,"1. Follow source → dataset → artifact details and open Studio. 2. Add a title, scope text and a detail table with the intended fields. 3. Add a case-count summary and a status chart. 4. Use a calculated or conditional display only where it explains a real rule. 5. Save Draft and open the saved current-data preview. 6. Inspect print/PDF pagination and the table/visual boundaries.","Show count 3, amount 2000, status breakdown and readable saved output.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-05,Vista,Review a saved report and run its published version,,,,Artifact = Training Case Operations saved revision; Author preview = Current saved layout with current authorized rows; Checker preview = Independent preview of the submitted exact revision; Run parameters = Only offered values on the published report,"Report Catalog / Report Studio → selected report → review, publish and run","1. The author saves and previews the intended revision, then submits. 2. The independent reviewer opens that record, inspects dataset and current preview and records the decision. 3. Publish the eligible approved version. 4. Run the published report and inspect My Report Runs. 5. Open the generated output and compare values, headers and pages. 6. For a later revision, create/save/review/publish it explicitly.","Show latest versus published version, the independent decision and an actual run output.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-06,Vista,Compose a dashboard and schedule controlled report/visual versions,,,,Dashboard = Training Operations Dashboard; Tile 1 = Published Training Case Operations summary block; Tile 2 = The published status comparison block or permitted second report tile; Layout = Two half-width tiles where the offered grid supports it; Schedule operation = Run published Vista dashboard,Vista → Dashboards → composition; Scheduler → Job Definitions,"1. Select published visuals and place them in a clear dashboard order. 2. Preview and inspect both populated and empty results. 3. Save, independently review and publish the dashboard. 4. Create a Scheduler job using the matching report/dashboard operation and selected published content. 5. Preview the job, review/publish it and execute a controlled run. 6. Inspect every tile/report result before declaring dashboard success.","Show dashboard publication, pinned report tiles, job preview and the resulting producer references.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-07,Vista,Configure the eight supported chart styles with typed fields,,,,"Prepared analytical fields = period TEXT; series TEXT; amount NUMBER; x NUMBER; Supported styles = Bar, column, line, area, donut, pie, stacked, scatter; Stacked chart = Category period; series field series; value amount; Scatter chart = Numeric x and amount; compatible aggregation; Format = Currency USD with 2 digits, or the offered decimal/percent format",Vista → Create Report → source/dataset selection → report details → Report Studio,"1. Open a saved report using the prepared analytical dataset. 2. Add a stacked chart with period, series and amount. 3. Add a scatter chart using numeric x and amount. 4. Set ordering and numeric format, save and reopen. 5. Preview compatible styles and one prepared invalid configuration.","Show the saved chart configuration, numeric types, ordering, format and a rejected incompatible selection.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-08,Vista,Recover a private report working copy and reconcile a changed base,,,,"Published base = Training Case Operations current version; Private change = Add a draft heading: Training revision in progress; Recovery context = Same authorized author, tenant and saved base revision","Report Catalog / Report Studio → selected report → review, publish and run",1. Open the published training report and create the permitted successor/working copy. 2. Make the named heading change and save the recovery copy. 3. Leave and reopen using the offered recovery action. 4. Compare the prepared stale-base example before accepting recovery. 5. Save the intended successor and preview before later review.,"Show private recovery, author/base identity, version conflict and the unchanged earlier publication.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-09,Vista,Publish a report successor without silently changing earlier outputs,,,,Current publication = Training Case Operations version 1; Successor change = Add the OPEN-only filter in a new draft; Reason = Adopt a reviewed filtered report version,"Report Catalog / Report Studio → selected report → review, publish and run",1. Open version 1 and retain its definition/output references. 2. Create the offered new version and add the OPEN filter. 3. Preview two expected rows / 1500 and submit. 4. Have the checker independently preview/review and publish the successor. 5. Compare an earlier run with a new run and inspect lifecycle state.,"Show two artifact versions, their saved filters, review evidence and separately pinned output history.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-VISTA-10,Vista,Refresh source data and distinguish changed rows from changed definitions,,,,Connection = Published Training Case Records; Input change = Change CASE1002 amount from 500 to 600 in the approved synthetic source; Expected live totals = OPEN amount 1600; all rows amount 2100,Vista → Sources & datasets → Connections → New connection,1. Record the prepared report’s original three rows and total 2000. 2. Have the approved source owner change the synthetic second amount to 600. 3. Run the registered source refresh and inspect its result. 4. Preview/run the report against current authorized rows. 5. Reconcile the dataset/report contract versions with the new data receipt.,"Show original/current rows, source refresh receipt, stable or changed schema contract and the correctly recalculated report.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-PULSE-01,Pulse,Select sources and datasets before naming the template,,,,Primary dataset = Published Training Case Summary; Key = record_id; preview CASE1001; Merge mappings = recipient.fullName ← name; correspondence.reference ← record_id; Related collection = items; match related case_id to primary record_id; order by item_id; Prepared related rows = CASE1001 has two items; CASE1003 has no items,Pulse → New email/letter → source/dataset selection → artifact details,"1. Pick the approved source(s) and eligible dataset(s). 2. Enter the template name, channel and basic details. 3. Save the primary dataset and primary record-key binding. 4. Add the related-items dataset and parent/child key mapping when required. 5. Reopen the saved binding and preview CASE1001.","Show source, dataset, artifact details, primary key and saved related mapping.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-02,Pulse,Author a responsive email with reusable and repeated content,,,,Template name / code = Training Case Update / TRAINING_CASE_EMAIL; Subject = Update for {{recipient.fullName}}; Body = Greeting; {{correspondence.reference}}; two-column next steps; repeated items; Related fallback = No related items are available.; Preview = CASE1001 and CASE1003; desktop and narrow width,Pulse → Email templates → selected draft → Email Studio,"1. Open the saved email draft with its dataset binding. 2. Add a clear greeting, case fields and a business next action. 3. Insert a related-record section and reusable content where appropriate. 4. Save Draft and preview CASE1001. 5. Inspect a narrow view, long text and a record with no related rows. 6. Correct the draft and save/preview the resulting revision again.","Show resolved subject/body, multiple related rows and the empty-collection layout.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-03,Pulse,Author and paginate a letter with stable repeated sections,,,,Name / code = Training Case Letter / TRAINING_CASE_LETTER; Page / margin = A4 / 20 in the offered page controls; Blocks = Greeting paragraph; correspondence reference; repeated items; explicit section break where needed; Long-data sample = Prepared collection of 50 permitted synthetic rows; Empty sample = The prepared no-item record,Pulse → Letter templates → selected draft → Letter Studio,"1. Create the letter using its saved source/dataset binding. 2. Set page geometry and place heading, body and footer. 3. Insert parent fields and the related table/section. 4. Add permitted page breaks and reusable content. 5. Save and inspect the saved PDF/output preview. 6. Repeat with a prepared long-data case and correct any clipping before review.","Show normal and multi-page output, the resolved record fields and related rows.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-04,Pulse,"Review, publish and generate the exact template version",,,,Template = Exact saved Training Case Email or Letter version; Preview result = READY proof for the author’s exact saved revision; Checker = Eligible independent reviewer with their own current preview; Generation record = CASE1001 and offered runtime values,"Pulse → selected template → governance, publish and generation actions","1. Save and preview the intended template revision. 2. Submit and complete the configured endorsement/independent approval stages. 3. Publish the approved version. 4. Generate output for the exact primary record using the published template. 5. Inspect the generated subject/body or complete letter PDF. 6. For later changes, create a new version and repeat the applicable governance.","Show version, review decisions, publication and the actual generated artifact.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-05,Pulse,"Trace output, dispatch, notifications and Custodia handoff",,,,Generated output = The returned Training Case Update email or letter output; Delivery channel / destination = An approved configured training channel and controlled recipient; Notification outcome = View outcome; Mark as read separately; Custody context = Approved class and case/reference for the output,Pulse → generated output; Delivery attempts; Operator inbox; Custodia Handoffs,"1. Inspect the generated artifact before any release. 2. Use only the offered configured delivery/capture action for the approved channel. 3. Inspect Delivery attempts and the producer/provider reference. 4. For Custodia, request the output handoff and follow its retained document reference. 5. Open a recipient notification/email outcome link with the eligible profile. 6. Use Mark as read separately and retain support correlation for a persistent failure.","Show output reference, dispatch status, Custodia document and current notification destination as separate facts.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-06,Pulse,Schedule email and letter generation with explicit ownership,,,,Operation = Generate published Pulse email or Generate published Pulse letter; Artifact = Exact eligible published template/catalogue version; Primary key = CASE1001; Email-only inputs = Approved sender and controlled test recipient where required; Execution owner = Selected approved subject/domain with access to primary and related data,Scheduler → Job Definitions → matching Pulse operation,"1. Select the matching registered operation before selecting the template. 2. Enter the record key, execution owner and operation-specific inputs. 3. Save and preview, then complete independent job review/publication. 4. Execute one controlled job and inspect its Pulse output reference. 5. Create/review/publish the intended one-time or recurring schedule. 6. Inspect failure, retry/rerun and audit using the Scheduler handbook.","Show the job’s pinned template, current record preview, run and Pulse output.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-07,Pulse,Create and preview a data-bound message template,,,,Template name / channel = Training Short Notice / offered SMS or message channel; Body = Hello {{recipient.fullName}}. Your case update is ready.; Language / provider template = The offered language and configured provider-template reference where required,Pulse → Templates → Create message template / Message templates,"1. Choose the offered message channel and prepared dataset. 2. Enter the short body with the saved recipient placeholder. 3. Save and preview the current training record. 4. Submit, independently review and publish the exact version.","Show the message body, saved binding, resolved preview and separate publication/provider readiness.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-08,Pulse,Verify parent-to-related-row binding and long collections,,,,"Parent / collection = CASE1001 / items; Columns = item_id and description, plus offered amount where needed; Ordering / bounds = Order by item_id; prepare zero, two and 50-row examples",Pulse → New email/letter → source/dataset selection → artifact details,1. Inspect the primary key and related match field in the saved contract. 2. Preview CASE1001 with two known item IDs. 3. Preview the empty prepared record. 4. Use the authorized long-data fixture and inspect all generated pages/rows.,"Show parent identity, match/order fields, zero/two/50-row outcomes and generation snapshot lineage.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-09,Pulse,Revise a published template and adopt the new version deliberately,,,,Published base = Training Case Update version 1; New wording = Add the approved next-step explanation in version 2; Comparison = Compare accessible versions using the offered action,"Pulse → selected template → governance, publish and generation actions",1. Open the published template and create the supported new draft version. 2. Change the next-step wording and save. 3. Compare accessible versions and preview the saved successor. 4. Complete independent review/publication. 5. Review dependent catalogue/Scheduler bindings before adoption.,"Show both versions, the comparison, successor preview/review and dependent adoption references.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-10,Pulse,Recover a queued or failed template preview,,,,Preview request = Current exact saved template revision; State = PENDING/RUNNING/READY/FAILED as actually returned; Recovery = The permitted retry/status operation for that same request,"Pulse → selected template → governance, publish and generation actions","1. Save the intended template revision and request preview once. 2. Inspect status and the configured preview worker’s operational health. 3. Read the prepared stale/failed attempt and its reason. 4. Use the offered recovery action, then inspect the resulting output against the saved revision.","Show request/revision, queued versus ready state, recorded failure and the valid recovered output.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-11,Pulse,Configure workflow notifications and trace the inbox outcome,,,,Channel = The offered approved email/in-app channel; Rule event = An offered workflow outcome event; Recipient = The permitted target user/profile/assignment selector; Template / next action = Approved notification content and originating-record outcome link,Pulse → Channels & rules; application bell / inbox,1. Open the current channel and rule configuration. 2. Select eligible recipient and approved content/link behaviour. 3. Complete the rule’s supported change/review process. 4. Use the prepared business event and inspect its notification. 5. Open the outcome and mark the notification as read separately.,"Show rule/event/recipient, queued or delivered state, inbox item and correct originating record.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-12,Pulse,Retain generated correspondence as a governed Custodia document,,,,Output = READY Training Case Letter PDF; Custody class / metadata = Approved training correspondence class and required reference fields; Business context = The authorized training case/reference,Pulse → generated output; Delivery attempts; Operator inbox; Custodia Handoffs,"1. Open the READY letter output and retain its checksum/output reference. 2. Choose the approved custody class, required metadata and authorized case context. 3. Submit the offered custody action and follow processing. 4. Open the admitted document/version as an eligible user.","Show output checksum, handoff receipt, admission state and authorized document version.",KRN-E-PULSE,,Awaiting client execution,,,
KRN-PULSE-13,Pulse,Prepare Pulse data · Register a bounded source connection and discover fields,,,,Name / code = Training Case Records / TRAINING_CASE_CONNECTION; Row path = data.records when the response is {data:{records:[...]}}; Authentication = The offered public or private credential-reference mode appropriate to the approved endpoint; Limits = 50 rows; 10 seconds; Scope = Tenant-field matching for tenant data; public only for genuinely public synthetic data,Vista → Sources & datasets → Connections → New connection,"1. Inspect existing connections before creating another. 2. Save the connection draft with endpoint, authentication reference, row path and limits. 3. Run Test & discover; if queued, Check test result until it finishes. 4. Inspect the returned contract and sample rows against the endpoint. 5. Submit, obtain the independent current test/review and publish.","Show connection revision, private reference type, READY discovery and published contract.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-PULSE-14,Pulse,Prepare Pulse data · Define the source and publish a selected dataset,,,,Source = Training Cases from the reviewed connection; Dataset name / code = Training Case Summary / TRAINING_CASE_SUMMARY; Selected fields = record_id TEXT; name TEXT; status TEXT; amount NUMBER; Prepared rows = CASE1001 OPEN 1000; CASE1002 OPEN 500; CASE1003 CLOSED 500; Preview limit = 50,Vista → Source Definitions; Datasets → New dataset,"1. Create the source definition against the eligible connection/registered source. 2. Save/review/publish the source through its offered lifecycle. 3. Create the dataset, select the intended source(s) and explicit output fields. 4. Preview and compare 3 training rows, total 2000 and OPEN total 1500. 5. Save the dataset and have the independent reviewer preview the same saved model. 6. Publish and retain the dataset version/reference.",Show connection → named source → dataset as three distinct controlled records.,KRN-E-VISTA,,Awaiting client execution,,,
KRN-PULSE-15,Pulse,"Prepare Pulse data · Model joins, calculations and filters without changing the grain silently",,,,"Source main = Claims: (id 1, member 10, amount 12.5), (2,20,8), (3,null,4); Source lookup = Members: (id 10, name ""  alice  ""), plus a null-id row; Join = LEFT: main.member = lookup.id; Calculated outputs = claim_id; member_name = upper(trim(name)) with UNKNOWN fallback; double_amount = amount × 2; Safe ratio = amount / 0","Dataset → Dataset structure → Model sources, joins and calculations","1. Choose a primary source and add the required secondary source. 2. Select compatible keys and the join type. 3. Select named outputs and add a calculation with the offered expression controls. 4. Preview matched, unmatched, empty and zero-value cases. 5. Compare parent count before and after a one-to-many join. 6. Save, independently preview/review and publish the exact model.","Show join kind, preview cardinality and one calculation with its expected values.",KRN-E-VISTA,,Awaiting client execution,,,
KRN-SCHEDULER-01,Enterprise Scheduler,Define and preview an operation with an accountable owner,,,,Code / name = TRAINING_REPORT_JOB / Run training case report; Artifact = Training Case Operations published version; Execution owner / domain = Offered authorized training identity and domain; Policy = Timeout 300 seconds; max attempts 3 only when allowed; concurrency 1; Inputs = Only the operation’s offered typed parameters,Scheduler → Job Definitions → New job,"1. Choose the operation before its content. 2. Select published content, execution identity/domain and required inputs. 3. Save and Preview the job. 4. Inspect empty/missing input and owner-access failures before submission. 5. Have the independent reviewer preview and decide the saved revision. 6. Publish and inspect the exact version.","Show registered operation, owner, pinned content and non-executing preview.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-02,Enterprise Scheduler,Run once and reconcile the producer result,,,,"Job = TRAINING_REPORT_JOB current published version; Reason = Verify the prepared three-row training output; Expected original data = Three rows / total 2000; Evidence = Run, attempt, producer result and output",Scheduler → selected published job → Run; Runs → selected run,"1. Open the published job and inspect owner, content and inputs. 2. Request one run with a reason and retain its ID. 3. Open Runs and inspect queue/lease/attempt progress. 4. Follow the producer reference to report/output/source result. 5. Compare actual output and expected training values. 6. Inspect audit and retained attempt history.","Show admission, run, attempt and actual producer output.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-03,Enterprise Scheduler,Create a calendar-aware one-time or recurring schedule,,,,Code / job = TRAINING_HOURLY_REPORT / published TRAINING_REPORT_JOB; Trigger = INTERVAL; 3600 seconds; future anchor selected in the form; Zone = UTC; Misfire / grace = SKIP; catch-up limit 10 where applicable; grace 30 seconds; Calendar = Eligible published calendar where required,Scheduler → Schedules → New schedule; Business calendars,"1. Select the published job and enter the intended trigger. 2. Set zone and calendar, then preview future occurrences. 3. Inspect a calendar exclusion and any relevant daylight-saving boundary. 4. Choose missed-execution policy and small catch-up/grace bounds. 5. Save, independently preview/review and publish the schedule. 6. Inspect the first admitted run and correlate its nominal occurrence.","Show local/UTC preview, calendar effect, policy and one admitted occurrence.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-04,Enterprise Scheduler,"Choose retry, rerun, cancel, pause or retire correctly",,,,Run = Specific training run and attempt; Retry = Eligible attempt within current run policy; Rerun = Deliberately linked new execution; Cancel / pause / retire = Current permitted state-dependent action,"Scheduler → selected job, schedule or run → eligible actions","1. Inspect the failed/uncertain run and producer state first. 2. Use an automatic/eligible retry only under the published retry contract. 3. If a new execution is intended, use Rerun with its reason. 4. Use Cancel only when offered and inspect its acknowledged result. 5. Pause a schedule to stop new admission, then resume after resolving the cause. 6. Retire unused configuration through the supported action and inspect history.","Show the difference between original-run retry, linked rerun and paused future admission.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-05,Enterprise Scheduler,Govern queue capacity and inspect worker leases,,,,"Queue = Offered isolated training queue/domain; Concurrency = 1 for this isolated exercise; Worker = Actual heartbeat, identity and lease; Actions = Drain/resume worker; pause/resume queue",Scheduler → Queues; Workers; selected queue policy,1. Inspect queued/running work and worker heartbeat before changing capacity. 2. Create the supported queue-policy revision and preview its impact. 3. Complete the independent review and publication. 4. Inspect a run moving from queued to leased/running. 5. Use the offered pause/resume/recovery operation and inspect retained leases.,"Show queue policy impact, worker heartbeat and a claimed run.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-06,Enterprise Scheduler,Preview and admit only missing historical occurrences,,,,"Schedule = Prepared published hourly report schedule; Range = Three past hourly instants [start, start + 3 hours); Purpose = Missing-only recovery using current authorized data; Prepared gap = One existing occurrence and remaining missing occurrences; Reason = Recover isolated training gap",Scheduler → Backfills → New plan,1. Select the schedule and a small known training gap. 2. Preview and inspect every occurrence and existing-run state. 3. Submit the exact plan for independent preview/review. 4. Obtain a fresh approved-plan preview and Enqueue when eligible. 5. Follow the child runs and their producer results. 6. Use eligible pause/resume/retire actions to control further admission.,Show at least one existing occurrence preserved and one actual missing occurrence admitted when prepared.,KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-07,Enterprise Scheduler,Run dependencies and resume from successful checkpoints,,,,Batch = TRAINING_CONTENT_BATCH; Success graph = source → report; report → letter and email; Child pins = Exact job version/hash for each node; Bounds = Max concurrency 2; timeout 3600 seconds; Checkpoint = Recorded child run and completed step,Scheduler → Batches → definition and selected execution,"1. Build the named steps and explicit dependencies using published jobs. 2. Preview inputs, owner authority and dependency validity. 3. Save, independently review/publish and start the controlled batch. 4. Inspect successful checkpoints and the first blocked/failed step. 5. On an isolated prepared run, Pause or Stop admission when permitted. 6. Resolve the cause, Preview the current run and Resume when eligible. 7. Inspect every child producer before declaring final batch success.","Show dependency graph, checkpoint, bounded pause/resume and retained successful work.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-08,Enterprise Scheduler,Verify the complete automation trail,,,,"Selected result = One training run, occurrence or batch; Definition / owner = Exact version used and execution owner; Lineage = Run → attempt → producer result/output; Verification = Offered integrity/lineage check",Scheduler → selected run → Audit / verification,"1. Open one completed or failed training run and follow its definition and occurrence. 2. Inspect owner, resolved inputs and all attempts. 3. Follow the producer/output reference and any rerun/backfill/batch parent. 4. Run the available audit verification and inspect its result. 5. Retain the scoped references and actual result in UAT/support evidence.",Show definition → timing/admission → run/attempt → producer → recovery/audit lineage.,KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-09,Enterprise Scheduler,Publish business hours and verify holiday/window boundaries,,,,Calendar / zone = TRAINING_BUSINESS_HOURS / UTC; Days = Monday–Friday; Windows = 09:00–12:00 and 13:00–17:00; Overrides = One training Monday closed; one Saturday 10:00–12:00,Scheduler → Business calendars; Schedules,1. Create the UTC calendar and weekday selection. 2. Enter the two windows and prepared overrides. 3. Preview and independently review/publish. 4. Bind the training schedule and inspect boundary instants. 5. Inspect the permitted retirement/dependency result.,"Show calendar version, schedule binding, boundary/holiday outcomes and dependency protection.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-10,Enterprise Scheduler,Schedule and verify one future execution,,,,Trigger = One-time; When / zone = Permitted future local time / explicit zone; Job = Published training report job,Scheduler → Schedules → New schedule; Business calendars,1. Choose the job and one-time trigger. 2. Select the actual future time and zone. 3. Preview and complete independent review/publication. 4. Inspect due execution in the isolated exercise.,"Show local/UTC plan, decision, occurrence/run and output.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-11,Enterprise Scheduler,Compare misfire recovery and daylight-saving timing,,,,Misfires = SKIP; FIRE_ONCE; CATCH_UP limit 2; Late sample = Hourly cadence with several missed instants; DST zone = America/New_York; Fold = Repeated local label may map to two UTC instants,Scheduler → Schedules → New schedule; Business calendars,"1. Open the prepared hourly variants. 2. Preview all three policies for the same missed interval. 3. Open the separate transition-day zone-aware preview. 4. Compare requested local time, resolved local time and UTC/shift/fold fields.",Show bounded misfire previews and explicit DST local/UTC interpretation.,KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-12,Enterprise Scheduler,Resume a partial batch from durable step checkpoints,,,,Batch run = Prepared source/report-success and downstream-failure run; Checkpoints = Successful predecessor step results; Resume = Eligible failed/pending continuation,Scheduler → Batches → definition and selected execution,1. Open the prepared partial-failure run. 2. Follow successful child outputs and failure reason. 3. Correct the isolated prerequisite and resume through the offered action. 4. Compare retained and newly admitted child runs.,"Show original run, step checkpoints, corrected failure and resulting child lineage.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-13,Enterprise Scheduler,Resolve current dataset values into typed job inputs,,,,Source = Published authorized dataset/key; Mapping = Declared typed job-input fields only; Record = CASE1001 when required by the operation; Before / after = Prepared amount 1000 then authorized source update,Scheduler → Job Definitions → New job,1. Open offered input-mapping controls. 2. Select dataset/key and compatible fields. 3. Preview CASE1001 and inspect resolved values. 4. Run the eligible job and inspect captured input provenance.,"Show typed contract, saved mapping, preview and run input provenance.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-14,Enterprise Scheduler,Run published Vista report · job through output,,,,Operation = Run published Vista report; Content = Training Case Operations; Execution owner = Approved current training subject/domain; Inputs = Only this operation’s declared values,Scheduler → Job Definitions → New job,"1. Choose Run published Vista report in Job Definitions. 2. Select Training Case Operations and authorized execution context. 3. Preview, submit, independently review and publish. 4. Run once and retain the durable reference. 5. Inspect operation-specific output.","Show operation, artifact pin, owner, inputs, decision, run and Vista output and expected report population.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-15,Enterprise Scheduler,Run published Vista dashboard · job through output,,,,Operation = Run published Vista dashboard; Content = Training Operations Dashboard; Execution owner = Approved current training subject/domain; Inputs = Only this operation’s declared values,Scheduler → Job Definitions → New job,"1. Choose Run published Vista dashboard in Job Definitions. 2. Select Training Operations Dashboard and authorized execution context. 3. Preview, submit, independently review and publish. 4. Run once and retain the durable reference. 5. Inspect operation-specific output.","Show operation, artifact pin, owner, inputs, decision, run and Dashboard output with pinned tile/report lineage.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-16,Enterprise Scheduler,Generate published Pulse email · job through output,,,,Operation = Generate published Pulse email; Content = Training Case Update; Execution owner = Approved current training subject/domain; Inputs = Only this operation’s declared values,Scheduler → Job Definitions → New job,"1. Choose Generate published Pulse email in Job Definitions. 2. Select Training Case Update and authorized execution context. 3. Preview, submit, independently review and publish. 4. Run once and retain the durable reference. 5. Inspect operation-specific output.","Show operation, artifact pin, owner, inputs, decision, run and READY email/MIME output; send remains separate.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-17,Enterprise Scheduler,Generate published Pulse letter · job through output,,,,Operation = Generate published Pulse letter; Content = Training Case Letter; Execution owner = Approved current training subject/domain; Inputs = Only this operation’s declared values,Scheduler → Job Definitions → New job,"1. Choose Generate published Pulse letter in Job Definitions. 2. Select Training Case Letter and authorized execution context. 3. Preview, submit, independently review and publish. 4. Run once and retain the durable reference. 5. Inspect operation-specific output.","Show operation, artifact pin, owner, inputs, decision, run and READY PDF, page count and checksum; delivery remains separate.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-SCHEDULER-18,Enterprise Scheduler,Refresh published source connection · job through output,,,,Operation = Refresh published source connection; Content = Training Case Records; Execution owner = Approved current training subject/domain; Inputs = Only this operation’s declared values,Scheduler → Job Definitions → New job,"1. Choose Refresh published source connection in Job Definitions. 2. Select Training Case Records and authorized execution context. 3. Preview, submit, independently review and publish. 4. Run once and retain the durable reference. 5. Inspect operation-specific output.","Show operation, artifact pin, owner, inputs, decision, run and Owner refresh receipt and current source evidence.",KRN-E-SCHEDULER,,Awaiting client execution,,,
KRN-CUSTODIA-01,Custodia,"Configure the content type, metadata and capture template",,,,Content type = TRAINING_EVIDENCE / Training evidence; Schema = TRAINING_REFERENCE / Training reference schema; Field = reference / Reference / TEXT; Constraints = Required yes; multiple no; maximum values 1; maximum text length 40; Permissions / reviewer = Offered metadata read/edit permissions and eligible independent reviewer,Custodia → Document classes/content types; metadata schema; entry templates,1. Inspect the approved class/type and its format/size rules. 2. Define the required typed schema fields and controlled vocabulary references. 3. Complete the applicable schema/type review and effective publication. 4. Create/select an entry template with intentional defaults. 5. Open capture as a contributor and inspect the resulting required fields.,"Show type policy, typed required fields and the capture form generated from that schema.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-02,Custodia,Upload and resolve the document’s processing stages,,,,File = training-evidence.pdf containing synthetic text only; Title / type = Training evidence 001 / approved Training evidence class; Metadata = reference = SYN-001; Context = Selected authorized training record/reference,Custodia → Document library → Upload → selected document → Processing,"1. Select files, remove unintended entries and review their type/business details. 2. Upload and inspect each per-file result. 3. Open Processing and inspect Receive, Security screening, Extraction, Classification, Metadata, Validation, Policy review, Indexing and Custody in order. 4. Resolve permitted metadata/classification errors or route security failures to the processing owner. 5. Refresh the current version and open the permitted preview/search entry.",Show per-file upload result and the first unresolved/resolved processing stage.,KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-03,Custodia,"Control checkout, check-in and exact-version review",,,,Document = Training evidence 001 current admitted version; Checkout = Current authorized editor; Replacement = training-evidence-v2.pdf with a second synthetic paragraph; Reason = Correct the training evidence,Custodia → selected document → version and review actions,1. Open the document and inspect its current version and checkout state. 2. Check out through the permitted action and retain ownership. 3. Check in the intended training replacement with a clear version reason. 4. Request/complete the required independent review of that exact version. 5. Compare current and earlier versions and their history.,"Show checkout owner, new version, exact-version decision and preserved prior history.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-04,Custodia,Review bounded sharing and exact-version redaction,,,,Share target = Eligible named training recipient; Scope / expiry = The exact document/version and a permitted short validity bound; Redaction example = Page 1; a small rectangle around synthetic text only; Reason / reviewer = Hide the training reference / eligible different reviewer,Custodia → selected document → sharing / page viewer / redaction,"1. Request a bounded share for the reviewed training document. 2. The eligible independent reviewer decides the share request. 3. Open Shared with me as the named recipient and test permitted actions. 4. In the exact-version page viewer, submit a small training redaction region with its reason. 5. After independent redaction review, inspect the rendered masked page. 6. Compare the permitted export representation before releasing any file.","Show exact version, bounded recipient grant, independent redaction decision and rendered mask.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-05,Custodia,Inspect retention and legal holds before disposition,,,,Policy = TRAINING_30_DAYS / 30-day training retention; Binding = Training evidence 001 / approved policy; Holds = Training hold A and Training hold B; Release = Only hold A through its reviewed release,Custodia → selected document → Retention / legal hold; Disposition readiness,"1. Inspect current retention, holds, versions, exports and archive copies. 2. Apply/review the required retention or hold using the supported action. 3. Use Disposition readiness to inspect an eligible disposable training target. 4. Where separately authorized, submit disposition and obtain independent review. 5. Execute only the offered current approved action and its exact confirmation. 6. Read back retained history and execution result.",Show a hold/retention blocker and disposition readiness; execute destruction only in the separately authorized disposable rehearsal.,KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-06,Custodia,Generate an approved export and track archive retrieval,,,,Export = Training evidence export 001; Content mode = The offered original or redacted rendition mode; Reviewer / reason = Eligible independent reviewer / hand over synthetic training evidence; Archive destination = Configured eligible archive provider/location,Custodia → Governed exports; Export reviews; archive transfer/retrieval,"1. Select exact versions, representation, purpose and permitted supplements. 2. Submit and have the reviewer inspect the current snapshot and validity. 3. Execute the authorized generation and wait for verified package status. 4. Download through the current authorized action and inspect its identity/checksums. 5. For an approved archive workflow, transfer the specified package and inspect the separate receipt. 6. Request/review retrieval when needed and inspect the returned copy and validity.","Show reviewed manifest, generated checksum, release state and any separate archive receipt.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-07,Custodia,Create an entry template and capture typed defaults atomically,,,,Template = TRAINING_CAPTURE / Training capture; Suggested title = Training templated evidence; Default metadata = reference = DEFAULT; Reviewer = Eligible independent template reviewer,Custodia → Entry templates; capture from selected template,"1. Select the approved class/schema and create TRAINING_CAPTURE. 2. Set the suggested title and reference default, then independently review. 3. Capture a synthetic file through the selected template. 4. Inspect completed capture and metadata read-back. 5. Inspect the prepared retirement or permission-denial example.","Show template review, typed default, document/version and absence of partial publication on failure.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-08,Custodia,Govern controlled vocabulary values used in metadata,,,,Vocabulary = TRAINING_EVIDENCE_KIND; Values = IDENTIFICATION; GENERAL; Field binding = A compatible schema choice field; Reason = Standardize evidence choices,Custodia → Controlled vocabularies; selected metadata schema,"1. Create the named vocabulary and two intended choices. 2. Submit with reviewer and reason, then complete independent review. 3. Bind the compatible schema field and review that schema change. 4. Capture a permitted value and inspect a prepared rejected outside value.","Show vocabulary/version, schema binding, allowed choice and validation of an unlisted value.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-09,Custodia,Assign document classification and demonstrate its access effect,,,,Definition = An approved training sensitivity classification; Assignment = Training evidence 001’s intended current version/document; Readers = One cleared and one ordinary unentitled training profile,Custodia → Classifications; document → Security,1. Inspect approved classification meaning and eligible readers. 2. Assign it to the training document through the offered action. 3. Open search/view as the cleared training profile. 4. Repeat as the prepared unentitled profile.,"Show definition, actual assignment and bounded allowed/denied access.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-10,Custodia,Promote a schema successor while retaining read-only old values,,,,Existing schema = TRAINING_REFERENCE version 1; Successor = Version 2 with an approved clarified field description/constraint; Review = Eligible independent successor decision,Custodia → Metadata schemas → selected schema successor,1. Open version 1 and inspect a document’s SYN-001 value. 2. Create permitted successor with current revision and reason. 3. Have eligible independent reviewer decide. 4. Read back old and new capture contexts.,"Show schema versions, successor review and unchanged historical metadata values.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-11,Custodia,"Search, save criteria and organize governed document relationships",,,,Search = reference SYN-001 plus offered title/type filters; Saved search = Training evidence search; Collection = Training evidence collection; Related document = Training evidence 002 with a permitted relationship type,Custodia → Search; Saved searches; Collections; Document relationships,1. Find the admitted document using reference/title/type filters. 2. Save the offered search criteria and reopen it. 3. Add eligible training documents to the permitted collection. 4. Create the allowed relationship to Training evidence 002 and reopen both records.,"Show search criteria, scoped results, collection and typed relationship references.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-12,Custodia,Review an exact document version and recover an interrupted decision,,,,Version = Exact current admitted training version; Review reason = Verify the synthetic evidence before business use; Decision = Eligible independent approve/reject or correction path,Custodia → selected document review; document activity,1. Open the selected version and start the permitted review. 2. Read assigned work as the eligible independent reviewer. 3. Decide with a meaningful reason after inspecting the evidence. 4. Reopen the document and notification outcome.,"Show version, assigned checkpoint, independent decision, owner effect and retained outcome receipt.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-13,Custodia,Review and verify a page redaction separately from private notes,,,,Page / region = Page 1; synthetic reference rectangle; Version = Training evidence 001 current version; Reason = Hide the synthetic reference for the training disclosure,Custodia → document page viewer; redaction review,1. Open the exact training version in the authorized viewer. 2. Add a private note and inspect its limited visibility. 3. Select the synthetic rectangle and submit a mask reason. 4. Independent reviewer inspects and decides. 5. Open the permitted rendered page and inspect export mode.,"Show exact region/version, private-note distinction, review and masked rendition.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-14,Custodia,"Receive, expire and revoke a bounded document share",,,,Recipient = Eligible named training user; Validity = A short permitted future expiry; Permission scope = The offered view/download rights for this document,Custodia → document sharing; Shared with me,1. Request a bounded share for the named training recipient. 2. Complete required independent review. 3. Sign in as that recipient and open Shared with me. 4. Use the prepared expiry/revocation example and refresh.,"Show share scope/decision, recipient access and post-expiry/revocation denial.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-15,Custodia,Start event-based retention from attributable business evidence,,,,Policy = An approved event-based training retention policy; Event = Actual configured training business event and occurrence reference; Document = Training evidence 001,Custodia → Event retention; document retention context,1. Select the approved event-based policy and applicable document. 2. Inspect the pre-event obligation state. 3. Use the prepared authorized event and inspect applicability. 4. Read retention state and due basis after resolution.,"Show event applicability, policy version, waiting/started state and retention due basis.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-16,Custodia,Review and execute eligible document disposition,,,,Target = Disposable synthetic training document only; Eligibility = Retention elapsed; no active legal holds; required current authority; Review / execution = Independent disposition decision and offered confirmation,Custodia → Disposition; selected document obligations,1. Open an isolated eligible training document and inspect all obligations. 2. Prepare and independently review the disposition request. 3. Use the permitted execution/confirmation only when current eligibility holds. 4. Inspect the certificate/audit and retained references.,"Show blockers/eligibility, exact review, execution result and retained certificate.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-17,Custodia,Revoke and dispose of a generated export package,,,,Export = Training evidence export 001 exact package; Action = Revoke or request package disposal as offered; Reason = End training disclosure availability,Custodia → Export packages; Export disposal,"1. Open the exact export and identify its source/manifest. 2. Use offered revocation and confirm new availability. 3. When eligible, request and independently review package disposal. 4. Execute or resume the allowed removal and inspect certificate.","Show package hash, revocation, reviewed disposal and scope-limited certificate.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-18,Custodia,Request a bounded archive retrieval and follow its returned copy,,,,Archive copy = Accepted transfer’s exact object/reference; Retrieval reason / reviewer = Inspect synthetic training evidence / eligible reviewer; Validity = Offered bounded retrieval window,Custodia → Archive retrieval,"1. Open the accepted archive transfer and inspect acknowledgement. 2. Request permitted retrieval with scope, reason and reviewer. 3. Complete required review and follow provider execution. 4. Open permitted content and inspect expiry/closeout.","Show archive acknowledgement, retrieval decision, available copy and expiry state.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-19,Custodia,Dispose of an eligible archive copy with retrieval protection,,,,"Copy = Exact accepted local archive copy; Blockers = Retention, holds and pending/approved retrieval authority; Confirmation = DELETE ARCHIVE COPY when the eligible form requests it",Custodia → Archive copy disposal,1. Identify the disposable accepted archive copy and its obligations. 2. Request disposal and complete independent review. 3. When eligible use the exact offered confirmation and execute. 4. Inspect certificate and retained acknowledgement/history.,"Show copy scope, blockers, review, execution and certificate.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-CUSTODIA-20,Custodia,Recover processing/index exceptions and investigate storage safely,,,,Failure = A prepared processing/indexing exception for a synthetic document; Batch bound = A small offered recovery limit; Investigation = The exact object/document/attempt references,Custodia → Processing operations; Index recovery; Storage investigations,"1. Open the isolated document’s failing stage and underlying attempt. 2. Inspect current state, age and allowed operator action. 3. Run only the permitted bounded recovery and inspect its receipt. 4. Recheck document/version, index and any related storage investigation.","Show owner-stage reason, bounded recovery, protected fresh work and resulting version/search state.",KRN-E-CUSTODIA,,Awaiting client execution,,,
KRN-MEDES-01,MEDES,Find the current member and open one exchange case,,,,Member = TRAINING_MEMBER_001 selected from the authorized current member search; Member version = The current returned reference/version; Case name / reason = Training evidence exchange / Collect and independently review evidence; Context = The current selected tenant and authorized worker assignment,MEDES → member context / exchange cases,"1. Search and verify the current member context. 2. Inspect existing exchange cases before opening another. 3. Create the case with the offered details and reason. 4. Reopen the case and inspect member, stage and linked evidence. 5. Retain its reference for document indexing and later correspondence.",Show member and case references as distinct identities with no automatic eligibility decision.,KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-02,MEDES,"Triage, split and index a PDF packet",,,,"Input = Admitted synthetic training PDF bound to the authorized context; Initial action = Begin intake with a reason; Decision = Single document or Needs splitting; Index values = Offered document type, classification, source/channel and current case/member reference",MEDES → Documents → Document Intake Queue,"1. Open the New intake item and inspect its admitted source document. 2. Begin intake, then confirm single document or mark for splitting with a reason. 3. For a packet, inspect page count and add titled child ranges in page order. 4. Review and complete the supported split. 5. Classify/index each eligible child with required metadata and the correct case context. 6. Read back intake and document history.","Show original packet, exact ranges, child identities and indexed case context.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-03,MEDES,"Request, submit and accept recipient-bound evidence",,,,Recipient = Eligible named training partner account; Maximum files = 2; Expiry = 24 hours; Requested evidence = Identity evidence and income evidence for the training case; Reason = Request synthetic training documents,MEDES → Secure Upload Workspace,"1. Find the intended eligible recipient and create the bounded request. 2. Open the saved request and copy its recipient-bound link through an authorized channel. 3. The named recipient signs in, reads the request and uploads the permitted files. 4. The recipient verifies the file set and selects Submit documents with a reason. 5. The receiving team checks each file’s security availability and selects Begin intake when eligible. 6. Open each admitted file and classify/index its business context.","Show recipient-bound access, upload versus submission, acceptance and intake handoff.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-04,MEDES,Review evidence and complete assigned case/eligibility work,,,,Case = Training evidence exchange; Document review = Exact current evidence versions; Case review = Start with a meaningful review reason; Eligibility = Eligible independent next-stage worker,MEDES → selected document review; Case work → Work Queue,"1. Complete required independent document reviews and inspect the case evidence list. 2. Start case review and inspect its saved workflow handoff. 3. Open My work or Available to claim and claim only eligible work. 4. Inspect the case and documents before deciding; use hold/information actions where justified. 5. At eligibility, complete the required outcome, date, checklist and reason as an eligible independent worker. 6. Read back case stage, task outcome and audit.","Show evidence review, task ownership and the separately attributable eligibility decision.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-05,MEDES,Prepare a complete packet before external delivery,,,,Case = Training evidence exchange with current member binding; Template = Prepared published MEDES training decision letter; Recipient / channel = Controlled training recipient and intended letter/fax mode; Attachments / fax cover = Selected authorized document versions; prepared cover where needed; Reason = Communicate the reviewed training outcome,MEDES → case correspondence → templates / fax covers / letter preparation,"1. Open correspondence from the current case and select eligible published content. 2. Set channel, recipient and destination and inspect included documents. 3. Generate and inspect the complete PDF/cover and attachments. 4. Complete required review and archive/custody handoffs. 5. Reopen the packet and inspect current readiness before choosing a provider.","Show case/template references, full packet, independent review and archive readiness.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-06,MEDES,"Dispatch once, reconcile status and record follow-up",,,,Packet = Exact reviewed training correspondence and attachments; Provider / destination = An approved configured training fax/email/provider route; Dispatch reason = Send the reviewed training packet; Result = Current pending/accepted/sent/failed/uncertain state returned by the owner,MEDES → approved packet → Delivery history; correspondence reply / customer follow-up,"1. Verify the approved complete archived packet and destination. 2. Select a compatible provider and inspect whether it is Live, Test or requires setup. 3. Queue live delivery or save the pending/test request as appropriate. 4. Inspect Delivery history, provider reference and later status. 5. After uncertain confirmation, use Retry same delivery request and read back the existing result. 6. Record the permitted correspondence reply/customer follow-up with its actual channel and reason.","Show the real delivery state, provider reference, same-request recovery and linked follow-up.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-07,MEDES,Split a six-page mixed packet into two attributable documents,,,,Source PDF = Synthetic six-page packet.pdf; Group 1 = Pages 1–2 / Identity evidence; Group 2 = Pages 3–6 / Income evidence; Source state = Current document/intake revision and classification,MEDES → Document Intake Queue → selected packet → Split,1. Open admitted packet.pdf and choose Needs splitting. 2. Define pages 1–2 and 3–6 with the two titles. 3. Prepare/execute through the permitted split action. 4. Inspect each child’s security/admission state and source lineage. 5. After admission continue intake/indexing on each child.,"Show six-page source, exact two groups, stable child identities, inherited classification and admission/lineage outcomes.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-08,MEDES,"Claim, release and hold assigned review work",,,,"Queue = My work / Available to claim / All authorized work only for eligible supervisor; Task = Training case’s current review task; Actions = Claim, release, hold, resume, request information as offered",MEDES → Case work → Work Queue,"1. Filter Available to claim by the training case/stage. 2. Open and claim with an attributable reason. 3. Use Hold and inspect its state, then Resume after the stated reason is resolved. 4. Release a separate prepared task where allowed and inspect eligible availability.","Show queue scope, task stage/owner, claim conflict protection and hold/resume/release history.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-09,MEDES,Exchange a case-bound secure message and recipient reply,,,,Message context = The authorized training case/member; Recipient = Eligible named partner or governed workgroup; Subject / body = Training evidence question / Please confirm the synthetic evidence reference.; Attachments = Only currently visible admitted training versions if offered,MEDES → Secure messages; Partner mailbox,1. Open the training case’s messaging action and choose eligible recipient. 2. Write and save the synthetic question. 3. Inspect current context/attachments and send through the permitted action. 4. Open as the named eligible recipient and reply. 5. Read the sender mailbox/history and separate read from business-review state.,"Show saved draft, recipient/context, sent message, reply and unchanged independent business-review boundary.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-10,MEDES,Close and reopen customer follow-up using actual response evidence,,,,Support activity = Customer needs a response / selected training case; Evidence link = Owned case-bound sent message or actual confirmed correspondence result; Outcome = RESPONDED only when current evidence supports it; otherwise explicit permitted NO_FURTHER_ACTION rationale; Revision = Current support activity version,MEDES → Customer follow-up / Support activity,1. Create the activity under the training case with a clear reason. 2. Use the bounded evidence picker to select the actual case-bound response. 3. Inspect can-close/current evidence and choose the justified outcome. 4. Read closure history and use Reopen when further work is required.,"Show activity, evidence scope/state, rejected premature closure and retained close/reopen history.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-MEDES-11,MEDES,"Read role dashboards, reports and current notification outcomes",,,,"Profile = Prepared member/partner, worker and supervisor profiles as applicable; Report scope = Training case/member and offered filters; Notification = A stage or outcome item for the same case",MEDES → Reports / dashboard; application bell / inbox,1. Select the permitted training profile and open its dashboard. 2. Apply the offered case/stage filters and reconcile a count with visible records. 3. Open the training notification and its case/work reference. 4. Switch only to another authorized prepared profile and compare visibility.,"Show selected profile, report/filter scope, count-to-record reconciliation and current outcome link.",KRN-E-MEDES,,Awaiting client execution,,,
KRN-NEXORA-01,Nexora,Author ordered lessons and completion requirements,,,,Course = Training Evidence Handling / TRAINING_EVIDENCE_COURSE; Required lesson = Read this lesson / TEXT / one minute / required; Optional lesson = Additional examples / permitted managed document or HTTPS link; Dependencies = Reviewed training assessment and certificate; Acknowledgement / feedback = The explicit offered statements and required feedback choices,Nexora → Content studio → Create course,"1. Create the course in Content studio and enter its information. 2. Add lessons in delivery order and complete their format-specific fields. 3. Mark required lessons and provide instructor notes separately. 4. Link the intended assessment, simulation or certificate and set acknowledgement/feedback. 5. Save, reopen and preview the learner view. 6. Submit the exact saved course for review.","Show lesson order, required flags, completion rules and the saved learner preview.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-02,Nexora,Build an assessment with automatic and written marking,,,,Assessment = Training Evidence Check / TRAINING_EVIDENCE_EXAM; Settings = Pass 75%; time limit 20 minutes; attempts allowed 2; Question q1 = SINGLE; Choose B; choices A/B; correct B; 2 points; Question q2 = SHORT_ANSWER; Explain your answer; 2 points; marking guide A complete answer; Total = 4 possible points,Nexora → Content studio → Assessment,"1. Create the assessment and enter threshold, time and attempt settings. 2. Add one choice question with correct answer(s) and one short-answer question with a marking guide. 3. If importing, inspect the resulting questions and types rather than trusting file acceptance alone. 4. Preview the questions and total point allocation. 5. Save and follow content review/publication for the exact version.","Show question types, marking guide and scoring settings without exposing hidden answers in learner presentation.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-03,Nexora,"Review, return and publish a specific content version",,,,Asset revision = Current Training Evidence Handling course/assessment revision; Review stages = Curriculum then Compliance where required; Correction example = Clarify the required lesson’s evidence instruction; Publication = Exact approved revision,Nexora → Content reviews; Compliance reviews; Learning publication; selected asset,"1. Open the submitted asset and read its content and completion requirements. 2. Inspect any policy, competency and prerequisite mappings. 3. Approve or request changes as the eligible independent reviewer. 4. If changes are requested, the author revises and resubmits the corrected version. 5. Complete the required compliance decision where configured. 6. Publish through Learning publication and inspect the learner catalog.","Show return/correction, independent approval, publication and the learner-visible revision.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-04,Nexora,"Assign training, paths and recurring campaigns",,,,Learning = Published Training Evidence Handling; Audience = Prepared eligible training learner/profile selection; Due / mandatory = A permitted future due bound / required for the training exercise; Cycle = Current assignment cycle; recurrence only where offered,Nexora → Training assignments; Training campaigns; Learning paths,"1. Inspect the published item or path before assigning. 2. Select the intended training learner/audience and due rules. 3. Save through the offered assignment/campaign action. 4. Open My learning as the learner and inspect version and due state. 5. For recurring campaigns, inspect cycle/renewal health and the next obligation. 6. Use Learning intelligence to compare assigned, completed and overdue counts.","Show manager assignment, learner receipt, pinned version, due date and cycle.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-05,Nexora,Complete learning and recover an interrupted attempt,,,,Learner = Prepared ordinary learner with the current assignment; Lesson = Required lesson in Training Evidence Handling; Attempt = Start current Training Evidence Check; Responses = q1 B; q2 The complete explanation; Completion = Required lesson plus final passing assessment and any configured acknowledgement/feedback,Nexora → My learning → assigned course; Assessments,"1. Open My learning and resume the assigned course. 2. Read the required lessons and record completion using the offered actions. 3. Start or resume the assessment attempt and save/submit its answers. 4. After interruption, reopen My attempts instead of starting another attempt immediately. 5. Complete any required simulation, acknowledgement and feedback. 6. Inspect final course completion and any certificate actually issued.","Show saved progress after resumption, attempt state and final completion requirements.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-06,Nexora,Grade written answers independently,,,,Attempt = The submitted training learner attempt and assigned assessment version; Automatic mark = q1 B = 2/2; Written mark = q2 justified 2/2 with comments; Boundary comparison = A hypothetical 1/2 written mark gives 3/4 = 75%,Nexora → Written-answer review → selected attempt,1. Open an Awaiting review attempt from Written-answer review. 2. Read each response beside its marking guide. 3. Enter the bounded score for each written/scenario answer and a meaningful review reason. 4. Submit the permitted grading action once. 5. Return as the learner and inspect the result and dependent course state.,"Show written response, marking guide, bounded score, reviewer and finalized outcome.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-07,Nexora,Author and run a branching simulation,,,,Simulation = Training Evidence Choice; Start choice A = Verify evidence → terminal debrief; score +100; Start choice B = Skip verification → remedial step; score +0; Pass score = 80; Debrief = Explain evidence checking and the chosen path,Nexora → Content studio → Simulation; Simulations,"1. Create the simulation with at least a start and terminal outcome. 2. Add choices with destinations, feedback and score effects. 3. Set the starting step and terminal debriefs; save and review/publish. 4. Run one learner path and inspect recorded choices and feedback. 5. Compare a different permitted path in a separate attempt when allowed.","Show starting step, branch choice, feedback, score and terminal debrief.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-08,Nexora,"Schedule sessions, manage attendance and discussion",,,,Course / instructor = Training Evidence Handling / eligible training instructor; Capacity = 1 for the isolated waiting-list exercise; Time / location = Permitted future browser-local start/end; training room or approved existing secure meeting link; Recording = An existing authorized secure recording when available; Discussion = Evidence question / scoped training question,Nexora → Live sessions; Discussions,"1. Schedule a session with its course, instructor, times and capacity. 2. Register an eligible learner; if full, inspect waiting-list state. 3. Cancel a training registration in the controlled example. 4. Record attendance through the permitted instructor/manager action and complete the session. 5. Add an authorized recording if available and inspect recipient access. 6. Open a discussion for the learning item and add a scoped question/reply.","Show saved session, registration/waiting list, attendance and scoped discussion.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-09,Nexora,"Trace policy change, readiness and credential evidence",,,,Policy mapping = Prepared evidence-handling policy version and its linked course; Readiness = The selected reviewed competency/readiness factors; Credential = Training certificate with configured 365-day validity where appropriate; Evidence scope = One training learner/course/cycle,Nexora → Policies & mappings; Competencies & readiness; Credential registry; Evidence & audit,"1. Inspect the policy’s linked published courses and any stale-mapping warning. 2. Revise/review affected learning before adopting the new policy mapping. 3. Inspect readiness factors and actual completion/result evidence. 4. Open an issued credential in Credential registry and inspect validity/state. 5. Use the permitted evidence/package operation for the selected scope. 6. Inspect activity audit for content decisions, assignment, attempt and credential events.","Show policy impact, readiness basis, credential state and the activity trail.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-10,Nexora,Assign an ordered learning path with remediation and recurrence,,,,"Path = Training Evidence Path; Sequence = Evidence Handling → Evidence Follow-up; Remediation = A separate published remedial course when the saved score condition applies; Campaign = A selected authorized audience, due rule and offered recurrence",Nexora → Learning paths; Campaigns / Learning administration,1. Prepare two published courses and a separate remedial course. 2. Create the ordered path and supported score-based branch. 3. Review/publish and assign the intended audience. 4. Inspect a prepared branch/cycle result and its history.,"Show published path/course pins, branch condition, audience and separate cycle obligations.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-11,Nexora,"Issue, verify and revoke an attributable learner credential",,,,Certificate definition = Training Evidence Certificate / validity 365 days; Course binding = Exact published credential reference; Issue = The completion-generated credential record; Revocation reason = End the isolated training credential’s validity where permitted,Nexora → Certificate templates; Credential registry,1. Prepare and review the certificate definition. 2. Bind it to the reviewed course. 3. Complete required learning and inspect the issued credential. 4. Use the permitted training revocation/expiry example and inspect the registry.,"Show definition, course binding, single issue, validity and retained revocation/expiry history.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-NEXORA-12,Nexora,Import questions and validate the saved assessment contract,,,,"Import format = Offered JSON or CSV under 1 MB; CSV header = prompt,type,points,choices,answers,modelAnswer; Total questions = At most 200 including existing questions; Question example = Choose B,SINGLE,2,A|B,B,",Nexora → Assessment authoring → question import,"1. Prepare the small training file using the offered format/header. 2. Import and inspect question type, points and answer/guide fields. 3. Compare total question count and fix reported validation. 4. Save, preview and complete the normal independent review.","Show file contract, parsed question fields, count bound and normal saved/reviewed assessment.",KRN-E-NEXORA,,Awaiting client execution,,,
KRN-ATLAS-01,Kernel Atlas,Sign in and select module and publication audience,,,,Account = Privately provisioned training editor/reviewer/client-reader accounts; Module = The intended Kernel training module; Audience = Internal for authoring; External for client review; Initial access = Complete required initial password change privately,Kernel Atlas → Sign In → selected module → Internal / External,1. Open the Atlas URL supplied by the deployment administrator and sign in. 2. Complete an initial password change when required. 3. Select the intended module in the header. 4. Use Internal for authoring and inspect the available workbenches. 5. Switch to External as an authorized reader and inspect the filtered view.,"Show selected module, role and the visible difference between internal and external content.",KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-02,Kernel Atlas,Write a requirement with testable acceptance criteria,,,,"Title = Evidence review must be attributable; Summary = An independent reviewer decides the exact submitted evidence version.; Specification = An ordinary author cannot approve their own submitted version; an eligible different reviewer records decision, reason and evidence reference.; Acceptance = Attempt ordinary self-review: denied; eligible independent decision: attributable outcome retained.; Source / approach = Approved training source reference / configuration or actual selected implementation classification",Atlas → Requirement Workbook → Create/Edit requirement,1. Create the requirement under the selected module. 2. Enter a complete obligation and acceptance criteria using the dedicated fields. 3. Add source and implementation/impact classifications. 4. Save as Draft and reopen the record. 5. Use the record’s submit action when the specification is ready for independent review.,"Show the requirement’s narrative, acceptance criteria, source and stable reference.",KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-03,Kernel Atlas,Use typed engineering registers instead of generic notes,,,,Function = Review evidence; actor eligible reviewer; trigger submitted version; Function step = Inspect evidence → compare author → decide → retain outcome; Business rule = Ordinary author identity must differ from reviewer identity; Typed owners = The returned requirement/function/rule references,Atlas → Engineering Registers; Capabilities; Functions & Rules,"1. Choose the correct record type in Engineering Registers. 2. Enter the complete behavior and any required owner reference such as FUNCTION:ID or UI_PAGE:ID. 3. Capture typed conditions, steps or contracts in their dedicated fields. 4. Save and reopen the record, checking all entered engineering fields. 5. Submit and independently review the exact revision.",Show one requirement → function → step/rule chain with the actual typed fields.,KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-04,Kernel Atlas,"Connect requirements, capabilities and exact test evidence",,,,"Relationship = Offered compatible IMPLEMENTED_BY, VERIFIED_BY or EVIDENCED_BY; Test case = Ordinary author self-review is denied; Run / execution = Actual selected environment, context and observed result; Evidence = Permitted result/screenshot/file reference and SHA256",Atlas → Traceability & RTM; Coverage & Evidence; selected record → Link Knowledge,1. Open the requirement and inspect its existing traceability. 2. Use Link Knowledge to connect the compatible capability/function and test case. 3. Record the test run and execution using their typed fields and actual result. 4. Link the permitted evidence record to the execution/requirement as supported. 5. Inspect Traceability & RTM and Coverage & Evidence.,Show design mapping separately from a test execution and its exact evidence.,KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-05,Kernel Atlas,Reconcile a business question without overstating coverage,,,,"Question = Does every review retain the exact evidence version?; Answer = Yes for the linked reviewed flow; identify any unverified branches explicitly.; Disposition = Already covered, clarification, partial support or new requirement as justified; Links / next action = Actual requirement/capability references and owner action",Atlas → BCQ Reconciliation,"1. Open or create the scoped BCQ record. 2. Enter the actual answer and business context. 3. Choose the disposition and justified coverage state. 4. Use Traceability to link existing requirements/capabilities or the required new work. 5. Enter the resolution note, save and submit for review.","Show question, answer, disposition, links and a concrete unresolved next action.",KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-06,Kernel Atlas,Build a readable document edition from governed sections,,,,"Edition = Training Evidence Operations Guide; Sections = 1 Prepare; 2 Submit; 3 Review; 4 Recover; Internal narrative = Full steps and outcomes for the training evidence journey; Knowledge links = DOCUMENTS relationships to actual requirement/function/rule records; External wording = Approved client-safe title, summary and complete narrative",Atlas → Document View → document edition → New Section,"1. Select the intended module and document edition. 2. Create a section with title, full narrative, parent and sequence. 3. Link the structured knowledge the section documents. 4. Preview the document reader and verify headings, order and completeness. 5. Save and independently review the section revisions.","Show a complete chapter, its order and its links to structured knowledge.",KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-07,Kernel Atlas,Review disclosure and publish an immutable client snapshot,,,,"Classification = SHAREABLE for the intended client-safe training sections; External fields = Explicit approved title, summary and body; Eligibility flag = Eligible for external publication only for intended shareable records; Publication = External audience; exact approved source revisions/hashes",Atlas → Governance & Reviews; Publications → Generate Document Snapshot,"1. Inspect source classification, external wording and eligibility. 2. Submit the exact source revision and have a different eligible reviewer decide it. 3. Open Generate Document Snapshot for the selected module and audience. 4. Inspect the output and source coverage before submission. 5. Submit Snapshot and have the eligible reviewer approve it. 6. Open the approved download as the client reader.","Show source approval, filtered external content, snapshot source hashes and separate snapshot approval.",KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-08,Kernel Atlas,Document workflow states and transitions with explicit runtime ownership,,,,Workflow = Training evidence review; States = Draft initial; Review; Approved terminal; Transitions = Submit Draft→Review; Approve Review→Approved; Runtime link = Actual governed Regulix definition/version if available,Atlas → Engineering registers → Workflow / State / Transition,"1. Create the workflow and define start/completion meaning. 2. Create owned initial/intermediate/terminal state records. 3. Create transition records with guard, action and side effects. 4. Link the actual runtime definition/evidence where it exists.","Show typed workflow/state/transition owners, review and an attributable runtime link.",KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-09,Kernel Atlas,"Record API, UI, configuration and validation contracts in typed registers",,,,API operation = Training evidence query; protocol/authentication/route/request/response/failures; UI page / field = Evidence review page; reference field; required text maximum 40; Action = Submit / permitted independent review; Configuration = Training review setting under its typed catalog owner,Atlas → Engineering registers → API / UI / Configuration,"1. Select each matching register type rather than a generic note. 2. Create typed parent then compatible child records. 3. Enter request/response, field bounds, action failures and configuration scope. 4. Save/reopen and link to the governing requirement/document section.","Show typed interface/page/catalog owners, persisted child fields and scoped disclosure.",KRN-E-ATLAS,,Awaiting client execution,,,
KRN-ATLAS-10,Kernel Atlas,Document exception handling and an executable operations procedure,,,,"Exception = Evidence review returned a stale-version conflict; Operations procedure = Reopen current record, inspect intervening review, reconcile and resubmit only needed change; Recovery evidence = Original conflict and current successful outcome where executed",Atlas → Engineering registers → Exception / Operations manual,"1. Create the concrete exception with trigger, symptoms and responsible owner. 2. Write ordered recovery actions and expected observations. 3. Link governing API/UI/function and the supporting document section. 4. When the isolated exercise is run, add actual run/execution/evidence records.","Show exception, ordered procedure, linked contract and actual evidence when available.",KRN-E-ATLAS,,Awaiting client execution,,,
KRN-IAM-01,Identity and Access Management,Create a domain and prove its mappings start empty,,,,Code / name = TRAINING_OPERATIONS / Training Operations; Reason = Create the isolated training access scope,IAM → Authorization → Domains,"1. Search Domains for TRAINING_OPERATIONS. 2. Create with code, name and business reason. 3. Eligible different reviewer decides on Domains. 4. Open its Mappings and the reverse profile/domain view.","Show domain creation, originating decision, zero forward/reverse links and absence of automatic runtime eligibility.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-02,Identity and Access Management,Create the reusable role and assignable profile,,,,Role code / name = TRAINING_CASE_READER / Training Case Reader; Profile code / name = TRAINING_OPERATOR / Training Operator; Reason = Prepare isolated training read access,IAM → Roles; Profiles,1. Create/review the training role on its owning record. 2. Create/review the training profile on its owning record. 3. Inspect each record’s current mapping sections. 4. Retain returned references for the mapping steps.,"Show role/profile identities, reviews and mapping state.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-03,Identity and Access Management,Map exactly one profile to the domain,,,,Domain = Training Operations; Profile = Training Operator; Reason = Allow Training Operator in Training Operations,IAM → Domains → Mappings; Profiles → Mappings,"1. Open the domain’s mapping editor and select Training Operator only. 2. Submit and inspect pending state. 3. Reviewer decides from the owning record. 4. Refresh domain and profile views, then inspect eligible assignment choices.","Show pending versus effective link, exact count and both directions.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-04,Identity and Access Management,Link profile and role without granting unrelated permissions,,,,Profile = Training Operator; Role = Training Case Reader; Reason = Attach the training read bundle,IAM → Profiles → Mappings,1. Open Training Operator and inspect existing roles. 2. Add Training Case Reader with reason. 3. Review on the owning profile record. 4. Inspect effective role list and eventual access explanation.,Show exact profile/role relationship and resulting current access explanation.,KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-05,Identity and Access Management,"Grant read permission and connect the menu, screen and control",,,,Role = Training Case Reader; Permission = Existing offered navigate/read/page requirements for a prepared synthetic training screen; Menu / page = The prepared Training Domain Directory or another isolated offered screen; Control = domain_name or another offered mapped field,IAM → Role permissions; Menu Access → Screens & controls,1. Inspect the screen’s actual navigation/page/data/control requirements. 2. Grant only intended read permissions to the training role. 3. Review role grant and required menu/permission/control relationships. 4. Evaluate the ordinary user’s selected context and perform the protected read. 5. Inspect one prepared missing-link case.,Show user→assignment→domain/profile→role→permission→menu/page/control chain and an explicit missing-link denial.,KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-06,Identity and Access Management,Create an administrator-initiated account and hand over enrollment,,,,User code = TRAINING_USER_01; Given / family name = Alex / Example; Email = A controlled deliverable training mailbox; Account type = The offered local/native option for this exercise; Reason = Create the isolated training operator,IAM → User Administration → User Accounts,1. Create the account with synthetic identity and controlled mailbox. 2. Reviewer decides on the originating User Account. 3. Open Progress and complete offered activation/enrollment steps. 4. Inspect enrollment message/output/delivery then hand the private link to the intended user. 5. User completes enrollment and first sign-in privately.,"Show account, progress, independent decision, enrollment delivery and actual first-sign-in outcome.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-07,Identity and Access Management,Classify and approve a self-registered applicant,,,,Applicant = Prepared training applicant with controlled mailbox; Domain / profile = Training Operations / Training Operator; Classification reason = Assign the applicant’s agreed training duties,IAM → User Accounts → Registration Requests,1. Open the verified training registration request. 2. Classify access using the explicit eligible domain/profile and reason. 3. Different eligible checker opens that same originating request. 4. Decide and inspect account creation/enrollment delivery lineage. 5. Applicant completes private enrollment/sign-in and selects permitted context.,"Show verified registration, classified scope, checker decision, resulting account and enrollment lineage.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-08,Identity and Access Management,Assign a bounded domain/profile and prove an ordinary read,,,,User = TRAINING_USER_01; Domain / profile = Training Operations / Training Operator; End bound = A permitted short future expiry for the exercise; Reason = Grant the agreed isolated read duties,IAM → User Accounts → selected account → Access,"1. Select the account and propose the exact bounded domain/profile assignment. 2. Independent reviewer decides on the user’s originating access record. 3. User signs in/selects that assignment. 4. Open the prepared screen, perform read and inspect denied edit. 5. Use prepared expiry/revocation and refresh.","Show pending/effective/ended assignment, session choice and read-versus-edit outcome.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-09,Identity and Access Management,Prove attribute filtering without confusing it with missing roles,,,,Target = Prepared isolated training screen; Condition = Selected domain is Training Operations; require all conditions; Comparison contexts = Two authorized test contexts with identical required read RBAC grants,IAM → Menu Access → owning screen → ABAC conditions,"1. Create the isolated policy with offered domain attribute and reason. 2. Reviewer compares target and before/after policy, then decides. 3. Use the matching approved ordinary context to read. 4. Use the prepared equal-RBAC failing context for the same read.","Show equal RBAC prerequisites, actual selected attributes and distinct ABAC allow/deny outcomes.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-10,Identity and Access Management,"Verify hidden, read-only, inherited and masked field behaviour",,,,Field = Synthetic registered field with actual IAM binding; Role = Training Case Reader or a separately prepared editor role; Modes = N no access; R read-only; E edit within role authority; F inherit; M mask where offered; Reason = Restrict the training field deliberately,IAM → owning screen → Controls & permissions → Edit field access,1. Select the actual owning screen/control and role. 2. Propose one intended supported field rule with reason. 3. Independent reviewer decides. 4. Reopen as affected ordinary user and inspect UI plus allowed response/write behaviour.,"Show control binding, reviewed mode, actual response scope and denied unauthorized write.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-11,Identity and Access Management,"Suspend, restore, expire and revoke access with history intact",,,,Target = TRAINING_USER_01 and its exact assignment; Operation = Offered suspend/restore/revoke/end action; Reason / bounds = Training duty ended or temporarily suspended,IAM → selected account / assignment → lifecycle actions,"1. Inspect account, session and assignment states. 2. Submit the intended lifecycle change and obtain required decision. 3. Verify actual user/context operation after application. 4. Restore only the intended eligible training access and inspect history.",Show account-versus-assignment effects and current runtime result.,KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-12,Identity and Access Management,Link a verified external identity and test federated access,,,,Provider code/name = Training Entra provider; Issuer / client ID = Exact provider issuer and registered application ID; Secret reference = Approved private reference only; Identity binding = Verified provider-issued subject or Entra Object ID → TRAINING_USER_01,IAM → SSO Providers; SSO Identities,"1. Confirm training provider application, callback and secret-reference setup privately. 2. Review provider configuration and verified external-subject link. 3. User signs in privately through that provider in a separate browser. 4. Select allowed internal domain/profile and perform a protected read.","Show verified stable identity link, successful provider return and internal allow/deny result.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-13,Identity and Access Management,Recover credentials and verify a sensitive action privately,,,,User = TRAINING_USER_01; Recovery channel = Controlled verified training mailbox; Sensitive action = An eligible prepared security action requiring fresh assurance,IAM → Account settings / personal security actions,1. Open the account’s supported recovery/change path. 2. Complete verification privately and inspect current progress. 3. Use Verify sensitive actions for the prepared eligible operation. 4. Perform only that permitted action and inspect audit/session outcome.,"Show safe account progress, assurance requirement and attributable action result without secret material.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-14,Identity and Access Management,Delegate a bounded duty and prove source expiry stops it,,,,Source = TRAINING_USER_01’s current bounded assignment; Recipient = A second eligible ordinary training user; Ends = A permitted future bound no later than source authority; Reason = Cover the isolated training duty,IAM → Access Governance → Delegations,1. Select the actual current source assignment and eligible recipient. 2. Propose end bound/reason and obtain independent decision. 3. Verify recipient context and intended protected operation. 4. Use prepared source-expiry/end case and refresh.,"Show source, recipient, bounded effective access and source-expiry denial.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-15,Identity and Access Management,Enforce conflicting duties and a scoped timed exception,,,,Policy = TRAINING_DUTY_CONFLICT; Roles = Prepared training author role and conflicting checker role; Exception = Exact policy + intended user + permitted short end; Reason = Approved isolated business exception,IAM → Separation of Duties; Timed Exceptions,"1. Review the domain/role conflict policy. 2. Use prepared normal assignment and profile-role conflict attempts. 3. Request/review a bounded exception for the exact user/policy only. 4. Verify eligible exception use, then expiry/revocation.","Show conflict, scoped reviewed exception and post-expiry restriction.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-16,Identity and Access Management,"Run a campaign, remove unjustified access and close it",,,,Campaign = TRAINING_REVIEW_01 / Training Operations review; Due = Permitted review due bound; Items = Prepared retained and removed assignment examples; Reason = Review continued training access need,IAM → Access Reviews; My Review Items,1. Create the scoped campaign and inspect actual assigned population. 2. Assigned reviewer retains justified access with reason. 3. Remove unjustified access through its required decision/application flow. 4. Resolve outstanding items and close when offered.,"Show population, retain/remove outcomes, effective removal and blocked premature closure.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-17,Identity and Access Management,Activate bounded JIT and pre-approved emergency access,,,,JIT = Eligible permission + permitted duration + business reason; Emergency = Exact pre-approved user/profile/permission eligibility; Activity = Only the intended protected training operation; Closeout = Revoke/expire and complete offered post-use review,IAM → Access Governance → Privileged Access,"1. Prepare eligible training permission and verify sensitive actions privately. 2. Request JIT, obtain different eligible reviewer decision and activate where offered. 3. Inspect a separate prepared emergency eligibility and its allowed request. 4. Perform only intended operation, then revoke/verify expiry and review recorded activity.","Show JIT review, emergency eligibility, bounded activation, actual operation and expiry/closeout.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-18,Identity and Access Management,Control dynamic menu availability and distinguish job scheduling,,,,Menu = Non-critical prepared Training Domain Directory; Window = Enabled with a permitted short start/end; inspect actual chosen values; User = Training user with otherwise equal valid grants,IAM → Advanced Configuration → Menu Schedules,1. Inspect current permitted menu and its availability state. 2. Propose/review bounded enabled/start/end values on that record. 3. Verify permitted user navigation and protected screen in/outside the prepared window. 4. Restore intended training configuration through the supported workflow.,"Show equal permission baseline, dynamic menu/route effect and clear menu-versus-job scheduling distinction.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-19,Identity and Access Management,Investigate sessions and follow current notification outcomes,,,,"Account = TRAINING_USER_01; Evidence = Sign-in success/failure, active session and session history; Notification = Training access-change submitted/approved item; Action = Permitted session/security operation only when needed",IAM → Reports → sign-in/session reports; application bell/inbox,1. Filter authorized sign-in/session reports for the training user. 2. Follow the relevant access change and review/audit reference. 3. Open the current notification outcome and mark read separately. 4. Use an intended permitted session operation if the isolated exercise requires it.,"Show sign-in/session history, current access decision, notification link and separate read state.",KRN-E-IAM,,Awaiting client execution,,,
KRN-IAM-20,Identity and Access Management,Demonstrate the named super-administrator exception separately,,,,Administrator = The explicitly assigned named Kernel Super Administrator account; Scope = Current tenant/profile and permitted protected action; Review = Same-person decision only where the configured named exception permits it; Reason = Explain and audit the isolated training administrator use,IAM → selected account/profile → protected administration,1. Inspect the actual administrator assignment and selected context. 2. Use only the intended permitted training change and current review action. 3. Read decision/audit actor and reason. 4. Compare a separate ordinary maker/checker example.,"Show actual exception assignment, bounded protected action and ordinary denial comparison.",KRN-E-IAM,,Awaiting client execution,,,
RG-01,Regulix,Govern a subscription approval policy and its replacement,,,,Policy code = RG_DEMO_SUBSCRIPTION; Policy name = Subscription onboarding review; Rule code = SUBSCRIPTION_ONBOARDING; Checker required = Yes for the first version; Reason = Demonstrate reviewed subscription onboarding,IAM approval rules → Rule Definitions,"1. Select the authorized policy author profile and open IAM approval rules. Inspect existing entries for SUBSCRIPTION_ONBOARDING. 2. Create the training policy with the values above and submit it with the reason. Retain the proposed change reference. 3. Attempt review using an ordinary author account, then reopen the same item as an eligible different checker. 4. Approve the policy on its originating record and reopen the effective policy. 5. Create a replacement version changing Checker required to No; submit and review that replacement. 6. Inspect an unrelated role change and its review requirements. 7. Retire the training policy through its governed action when the exercise is finished.","Show the policy proposal, reviewer decision, version 1, replacement version 2 and the originating business route. Keep the effective policy identity separate from the user or subscription identity.",RG-E01,,Awaiting client execution,,,
RG-02,Regulix,Create and evaluate the score-threshold decision table,,,,"Name / training code = Score threshold / RG_DEMO_SCORE_THRESHOLD; Definition family = Decision table; Input = score: number; Hit policy = FIRST; Rule row = score >= 700 → result = ACCEPT; Start evaluation input = {""score"":750}",Rule Design → DMN Library → Rule Definitions → Decision Logs,"1. Open Rule Design, enter the training name and choose the decision-table family. 2. Declare score as numeric, select FIRST, and add the accept row shown above. Save the draft. 3. Run the supported test/preview with score 750. Inspect the matched row and output. 4. Test 699, 700 and 701 separately. Retain the actual result for each. 5. Use the supported review/publication controls for the exact saved artifact. Reopen Rule Definitions. 6. Evaluate the eligible model again with score 750, then open the associated Decision Log. 7. If selecting an environment or alias, choose a configured reviewed binding rather than inventing an alias name.","Show the saved row, input 750, matched row, ACCEPT output, 699 no-match case, 700 boundary and the model reference in the evaluation history.",RG-E02,,Awaiting client execution,,,
RG-03,Regulix,Start and complete the exercised human-review process,,,,Process name = Training Human Review; Human stage = Review request; Assignment policy = Approved reviewer policy selected from the configured policies; Business key = RG-DEMO-HUMAN-001; Initial variables = {},BPMN Design → Process Definitions → Process Instances → Work Queue,"1. In BPMN Design build the review-to-end process and select the eligible assignment policy. Save and validate. 2. Complete the configured definition review/publication and select the eligible version in Process Definitions. 3. Start once with business key RG-DEMO-HUMAN-001. Record the returned instance reference. 4. Open Process Instances and select that instance. Inspect definition, business key, current task and assignment. 5. As the ordinary initiating profile, attempt the checker-only completion. 6. Open the same current task as an eligible checker and complete its required input. 7. Read back the instance and its history after completion.","Show the definition, the waiting instance, the denied initiator completion and the same instance completed by the eligible checker.",RG-E03,,Awaiting client execution,,,
RG-04,Regulix,"Follow event correlation, a decision gateway and four review stages",,,,"Process name = Training Routed Review; Input = Credit Score: number; Approved path sample = {""Credit Score"":750}; Default review sample = {""Credit Score"":650}; Review assignments = requester, risk, legal, finance, release; Event correlation = Configured event + scope + the instance business key; Service binding = Reviewed registered action with a completion contract",BPMN Design → Event Registry → Assignment Policies → Process Instances,"1. Prepare the process with the shown nodes and connect its reviewed decision, assignment, event and service dependencies. Validate the full graph. 2. Start the approved training version with Credit Score 750 and a unique business key. Complete the requester task. 3. Correlate the configured event using the correct scope and business key. 4. Use the permitted runtime advance action or configured worker. Inspect the returned decision and selected node. 5. Follow the service completion and inspect its result reference. 6. Start a second instance with Credit Score 650 and a different business key. Complete the requester and event steps. 7. Complete Risk, Legal, Finance and Release using the actual eligible stage identities. 8. Inspect both instance histories and compare their paths.","Show the two input payloads, event wait, gateway result, selected path, four assigned review roles and final histories.",RG-E04,,Awaiting client execution,,,
RG-05,Regulix,"Complete a staged case, its required tasks and milestone",,,,Case name = Training Evidence Case; Stage = Evidence review; Task A = Review documents; Task B = Confirm review outcome; Milestone = Evidence review completed; Business key = RG-DEMO-CASE-001; Case variables = A structured object matching the definition,Case Management Design → Case Definitions → Case Instances,"1. Create the named case, stage, two required human plan items and milestone. Configure the dependencies shown above. 2. Bind eligible assignment policies, validate, and complete the configured definition review/publication. 3. Start RG-DEMO-CASE-001 once and open its Case Instance. 4. Complete task A using the assigned reviewer and reopen the current case state. 5. Complete task B using the eligible assignee and inspect the stage/milestone timeline. 6. Prepare a separate case variant with a condition such as approved = true on task A. Start with that condition false. 7. Update the permitted case facts and use the supported sentry/advance action.","Show task A, task B’s entry dependency, the required stage, milestone, actual reviewer and final case history.",RG-E05,,Awaiting client execution,,,
RG-06,Regulix,Build the exercised weighted scorecard and reconcile its total,,,,"Name = Training Weighted Score; Factor credit = Weight 60; score 100 when credit >= 700, otherwise 20; Factor income = Weight 40; score 80 when income >= 50, otherwise 0; Bands = LOW: 0–49; HIGH: 50–100; Input = {""credit"":750,""income"":60}",Rule Design → Rule Definitions → Decision Logs,"1. Create the training scorecard in Rule Design and add the two named factors. 2. Enter each factor’s conditions and point scores, then add the LOW and HIGH bands. 3. Preview with credit 750 and income 60. Expand the factor result. 4. Save and complete the eligible artifact review/publication. Evaluate that exact version. 5. Inspect the scorecard result and associated log reference. 6. Change a factor only in a new draft version and compare the expected new total before adoption.","Show both factor definitions, weight total 100, input values, 60 + 32 = 92, HIGH band and the recorded model reference.",RG-E06,,Awaiting client execution,,,
RG-07,Regulix,Connect two decisions as a chain and dependency graph,,,,"First child = Training Credit Flag; Second child = Training Allow High; Root family = Chain or graph; Child selection = Each exact reviewed model and version/content reference; Start input = {""score"":750}",Rule Design → Artifact Graph → Rule Definitions → Decision Logs,1. Prepare and review both child tables with the shown inputs and outputs. 2. Create a chain using first followed by second; select exact child versions. 3. Preview/evaluate the eligible root with score 750. 4. Create the equivalent graph and make second depend on first. 5. Run the same input against the graph and inspect intermediate outputs. 6. Inspect root and child decisions in the available history.,"Show each child result, dependency direction, root final output and linked root/child history.",RG-E07,,Awaiting client execution,,,
RG-08,Regulix,Explain four policy-combining algorithms with the same facts,,,,"Policy deny-restricted = DENY when resource.class = restricted and subject.role != admin; Policy permit-active-read = PERMIT when action.name = read and subject.active = true; Facts = subject.role=user; subject.active=true; resource.class=restricted; action.name=read; Algorithm = DENY_OVERRIDES, PERMIT_OVERRIDES, FIRST_APPLICABLE or ONLY_ONE_APPLICABLE",Policy Set Library → Rule Design → Decision Logs,"1. Prepare the two policies and the structured input facts shown above. Inspect the order. 2. Evaluate the approved DENY_OVERRIDES example. 3. Evaluate the equivalent PERMIT_OVERRIDES example. 4. Evaluate FIRST_APPLICABLE with deny-restricted first. 5. Evaluate ONLY_ONE_APPLICABLE using the same facts. 6. Test subject.role=admin, subject.active=true, resource.class=public and action.name=write. 7. Open the evaluation trace and then explain the separate IAM/business enforcement boundary.","Show the same input facts, both matching policies, four combining outcomes and the separate enforcement boundary.",RG-E08,,Awaiting client execution,,,
RG-09,Regulix,"Test warning and breach boundaries, then inspect an incident",,,,Rule name = Training Review Deadline; Target = BPMN_ACTIVITY; Warning threshold = 1000 ms; Breach threshold = 2000 ms; Incident policy = SLA_BREACH; severity HIGH; Calendar / time zone = The approved values required by the intended obligation,SLA Library → SLA Policy Master → SLA Incident Policy → SLA Incidents,"1. Create or open the training SLA rule and enter the thresholds above. 2. Prepare the four valid preview inputs and the deliberately invalid started_at input. 3. Run the supported SLA test suite and inspect each case. 4. Explain the invalid-case result before presenting the suite summary. 5. Create the draft incident policy referencing this rule, then read it back. 6. For a live obligation, complete its required review and binding to the activity/calendar before waiting for a deadline. 7. Open an actual resulting SLA incident where one exists and inspect its source obligation and action history.","Show the exact thresholds, all five preview outcomes, saved incident-policy reference and the distinction between preview and a monitored obligation.",RG-E09,,Awaiting client execution,,,
RG-10,Regulix,Recover updates and retries without losing the original instance,,,,Selected instance = The existing waiting training instance; Variable change = postRouteNote = reviewing for the process example; Expected version = The current version returned by read-back; Request identity = The existing identity for an exact uncertain retry; Outcome reference = The recorded checkpoint and command receipt,Process Instances → Case Instances → Decision Logs,"1. Open a waiting process or case instance and record its current version and task. 2. Use the offered variable-update action to set the training note. Read back the result. 3. Inspect an exact replay of the same command in the prepared exercise evidence. 4. Inspect the deliberately stale update attempt. 5. Complete the permitted task with the eligible reviewer and retain the completion result. 6. Inspect the transport-restart recovery result in the prepared engineering evidence. 7. For a real uncertain external effect, inspect the producer result before initiating recovery.","Show the original instance, version change, stable retry receipt, rejected stale command and persisted completion result.",RG-E10,,Awaiting client execution,,,
KRN-CROSS-01,Cross-module,"Onboard an organisation, provision its tenant and admit an ordinary user",,,,Organisation = Example Services Training; Tenant = TRAINING_TENANT; Access = TRAINING_OPERATIONS / TRAINING_OPERATOR / TRAINING_CASE_READER,"Core: create/reuse the training organisation and verify contact/address ownership. → Tenant Engine: save onboarding, capture identity/commercial requirements and publish the eligible configuration. → Tenant Control Plane: inspect environment, entitlements, deployment and the permitted activation path. → IAM: create the empty domain, profile and role, then approve the explicit mappings and scoped user assignment. → Ordinary user: select the assigned context and open permitted menus, screens and actions. → Inspect the originating review, Pulse notification and audit references.","1. Core: create/reuse the training organisation and verify contact/address ownership. 2. Tenant Engine: save onboarding, capture identity/commercial requirements and publish the eligible configuration. 3. Tenant Control Plane: inspect environment, entitlements, deployment and the permitted activation path. 4. IAM: create the empty domain, profile and role, then approve the explicit mappings and scoped user assignment. 5. Ordinary user: select the assigned context and open permitted menus, screens and actions. 6. Inspect the originating review, Pulse notification and audit references.","Retain the onboarding and access evidence, then run the source/report or correspondence journey using the ordinary user’s permitted context.",Owning module evidence chapters,,Awaiting client execution,,,
KRN-CROSS-02,Cross-module,"Connect a source, model data, publish content and schedule its execution",,,,"Training rows = CASE1001 OPEN 1000; CASE1002 OPEN 500; CASE1003 CLOSED 500; Vista result = Three records / amount 2000; OPEN amount 1500; Pulse scalar mappings = recipient.fullName ← name; correspondence.reference ← record_id; Scheduler = Exact published artifact, operation and execution owner","Vista: publish an authorized connection and discover/register the source contract. → Vista: model and preview the dataset, then independently review the exact saved version. → Vista: author and preview the report/dashboard against the sample totals; independently review and publish. → Pulse: bind the supported fields and related items; author/preview/review/publish email and letter content. → Scheduler: preview/review/publish a registered operation job; run once before enabling timing. → Inspect dispatch/custody only where configured; exercise a revoked dependency and recover deliberately.","1. Vista: publish an authorized connection and discover/register the source contract. 2. Vista: model and preview the dataset, then independently review the exact saved version. 3. Vista: author and preview the report/dashboard against the sample totals; independently review and publish. 4. Pulse: bind the supported fields and related items; author/preview/review/publish email and letter content. 5. Scheduler: preview/review/publish a registered operation job; run once before enabling timing. 6. Inspect dispatch/custody only where configured; exercise a revoked dependency and recover deliberately.","Use the Scheduler desk for calendars, queue controls, bounded backfill and batch checkpoint recovery; record actual producer outcomes separately from dispatch.",Owning module evidence chapters,,Awaiting client execution,,,
KRN-CROSS-03,Cross-module,"Admit evidence, complete case review and retain the correspondence outcome",,,,"Document = Approved training class and metadata schema; Case = Current authorized member reference and case ID; Review = Required evidence/eligibility tasks and assigned reviewer; Communication = Published content, permitted recipient and custody class","Custodia: define/review the class/schema/template and admit a permitted training document. → MEDES: open/reuse the case for the current member and attach only eligible admitted evidence. → MEDES: request secure upload or split the prepared packet where needed, then complete admission. → MEDES/Regulix: follow the configured required review tasks and record the owning business outcome. → Pulse: generate the approved correspondence, inspect delivery and hand the permitted output to Custodia. → MEDES: record customer follow-up using actual response evidence and close or reopen through the supported action.","1. Custodia: define/review the class/schema/template and admit a permitted training document. 2. MEDES: open/reuse the case for the current member and attach only eligible admitted evidence. 3. MEDES: request secure upload or split the prepared packet where needed, then complete admission. 4. MEDES/Regulix: follow the configured required review tasks and record the owning business outcome. 5. Pulse: generate the approved correspondence, inspect delivery and hand the permitted output to Custodia. 6. MEDES: record customer follow-up using actual response evidence and close or reopen through the supported action.","Inspect case audit, evidence versions and correspondence together; use Custodia’s hold, disclosure and archive procedures for their separate lifecycle responsibilities.",Owning module evidence chapters,,Awaiting client execution,,,
KRN-CROSS-04,Cross-module,"Publish learning, grade the response and link its assurance evidence",,,,Assessment = Single choice 2 points + written answer 2 points; pass mark 75%; Learner = Assigned training user with eligible course/path; Engineering evidence = Authorized Atlas requirement/test/evidence references,"Nexora: author the course and assessment, prepare the exact answer key and independently publish. → Assign the published learning and complete it as the training learner. → Eligible grader: review the written answer and finalize the recorded outcome. → Inspect course completion, credential and any path/campaign/session obligations. → Atlas: create/select the authorized requirement, test case and evidence record for the documented obligation. → Record the learning outcome reference as permitted evidence and independently review the register/publication.","1. Nexora: author the course and assessment, prepare the exact answer key and independently publish. 2. Assign the published learning and complete it as the training learner. 3. Eligible grader: review the written answer and finalize the recorded outcome. 4. Inspect course completion, credential and any path/campaign/session obligations. 5. Atlas: create/select the authorized requirement, test case and evidence record for the documented obligation. 6. Record the learning outcome reference as permitted evidence and independently review the register/publication.","Record the learning and register results independently, then retest any corrected content or assurance gap before accepting the business obligation.",Owning module evidence chapters,,Awaiting client execution,,,
KRN-FLOW-IAM-01,Identity and Access Management,Copy menu access from one or more roles,,,,Target role = TRAINING_CASE_READER; Source roles = Prepared Training Navigation Reader and Training Detail Reader; Selected menus = Training Domain Directory only; Reason = Add the reviewed training read action,IAM → Menu Access → select target role → Copy from Roles,"1. Open the target role and record its current menus/actions. 2. Choose Copy from Roles and select both prepared source roles. 3. Select the training menu and inspect included versus skipped actions. 4. Deselect one source and inspect the recalculated result, then restore the intended selection. 5. Add to proposed changes and open Review Changes. 6. Submit the exact proposal and have an eligible independent reviewer decide it on the originating access record. 7. Refresh the ordinary training user’s context and verify the intended menu/action.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-IAM-01,,Awaiting client execution,,,
KRN-FLOW-IAM-02,Identity and Access Management,Bulk changes with mixed results and interrupted processing,,,,Selection = Two disposable training users and one prepared ineligible/protected row; Example operation = Assign Profile: Training Operations / Training Operator; Reason / end = Training batch assignment; offered optional end bound; Result file = iam-batch-results.json,IAM → User Accounts / Profiles / Roles → select rows → offered bulk action,"1. Select only the prepared rows and open Assign Profile. 2. Choose the domain/profile, enter the reason and select Review Selected Records. 3. Inspect the ineligible row and confirm only the intended ready rows. 4. During the prepared larger safe batch, choose Stop After Current Record. 5. Inspect SUCCEEDED, FAILED and UNCONFIRMED outcomes and download results before closing. 6. Choose Continue / Reconcile Remaining for ready/unconfirmed rows. 7. Resolve a genuinely failed row and prepare a fresh review for it only.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-IAM-02,,Awaiting client execution,,,
KRN-FLOW-IAM-03,Identity and Access Management,User Access Hierarchy investigation and drilldown,,,,User = TRAINING_USER_01; Context = Training Operations / Training Operator; Expected chain = Profile → Training Case Reader → approved read permission → menu/screen/control; Comparison = Prepared ended assignment or missing-link case,IAM → User Access Hierarchy,"1. Search for and open the training account in User Access Hierarchy. 2. Expand the selected domain/profile and inspect its assignment period. 3. Follow the profile’s roles, role permissions and related screen/menu references. 4. Inspect the prepared ended/missing link and its current effect. 5. Open the owning record, inspect its mappings/history, then use Back to return. 6. Perform the ordinary permitted read and a prepared denied action.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-IAM-03,,Awaiting client execution,,,
KRN-FLOW-IAM-04,Identity and Access Management,Personal-information contact preferences and enrollment selection,,,,"Person = The party linked to TRAINING_USER_01; Name / phone = Alex Example; approved synthetic phone value; Email = A controlled training mailbox; Preferences = Preferred contact=true; offered contact type/purpose; priority 1; valid current interval; Consent reference = Only an existing authorized consent decision, if applicable",Account menu → Personal information → email/phone → Contact preferences,1. Open Personal information and verify the linked person before editing. 2. Select the intended recorded name; add or edit an eligible email/phone. 3. Expand Contact preferences for that contact and inspect its current assignment. 4. Set the intended bounded preferences and save using the current revision. 5. Reopen the contact and compare current preference/period. 6. Inspect the account’s enrollment/reissue path without exposing private credentials.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-IAM-04,,Awaiting client execution,,,
KRN-FLOW-PULSE-01,Pulse,"Browser push opt-in, profile binding and unsubscribe",,,,Account / profile = TRAINING_USER_01 in Training Operator; Browser permission = Allow for the intended site after choosing Enable; Prepared event = An eligible training access-change notification; Read state = Mark as read separately from View outcome,Application header → bell → Browser notifications,"1. Sign in, select the intended profile and expand Browser notifications in the bell. 2. Choose Enable and allow the browser’s site permission. 3. Use the prepared eligible event and inspect the device/browser notification and foreground bell. 4. Open the notification and follow View outcome. 5. Mark the item as read, then choose Turn off for this browser. 6. In a separate prepared opt-in, switch profile or sign out and inspect current binding. 7. For a blocked browser permission, change the site notification setting and reload before enabling again.","Record browser permission/binding, prepared event, actual device observation if any, protected outcome and disabled/signed-out state. Never record private endpoint authentication keys.",FLOW-E-PULSE-01,,Awaiting client execution,,,
KRN-FLOW-PULSE-02,Pulse,Author and review the correspondence catalogue before generation,,,,Catalogue code / name = TRAINING_CASE_CORRESPONDENCE / Training case update; Template = Exact published Training Case Email or Training Case Letter version; Primary binding = Published Training Case Summary; key record_id; Scalar mapping = recipient.fullName ← name; correspondence.reference ← record_id; Related binding = items matched by case_id → record_id; item_id order; Runtime request = CASE1001,Pulse → Review & catalog → Correspondence Catalogue → New Correspondence,1. Open the catalogue and search for an existing training record before creating it. 2. Select the exact eligible published template and configure the supported input/data binding. 3. Save and preview with CASE1001 and the prepared empty-related record. 4. Submit the exact saved catalogue version for its required independent review and publication. 5. Create a correspondence request using the published catalogue and CASE1001. 6. Follow the producer job to its actual output and inspect content against the prepared rows. 7. Use configured dispatch or Custodia handoff only through its separate offered action.,"Retain catalogue/template/dataset versions, saved binding, preview, decision, request, output and any separate delivery/custody receipts.",FLOW-E-PULSE-02,,Awaiting client execution,,,
KRN-FLOW-PULSE-03,Pulse,"Suppressed, future and expired generation policies",,,,"Catalogue = Prepared isolated training correspondence; Generation policy = Allowed, then a separate suppressed training version; Suppression reason = Training suppression boundary demonstration; Validity = Future start and increasing end with explicit zone; compare current allowed interval; Consent / transport = Not evaluated / not authorized by this local-generation policy",Pulse → Correspondence Catalogue → selected correspondence → Generation Policy,"1. Open the isolated correspondence and inspect its current published policy. 2. Prepare a successor with the offered allowed policy and a valid interval; save/review/publish normally. 3. Request the prepared record inside the valid interval. 4. Use separately prepared suppressed, future and expired versions for negative requests. 5. Inspect a prepared queued job whose validity ends before claim/finish. 6. Read the request’s decision/timestamp/policy checksum and retain the prior version history.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-PULSE-03,,Awaiting client execution,,,
KRN-FLOW-PULSE-04,Pulse,Channel setup and provider-readiness boundaries,,,,"Channel = TRAINING_INAPP or another isolated offered channel; Name / active state = Training notification channel / intended active state; Rule event / recipients = Offered access-change event and eligible training recipient selector; Template/provider reference = Approved content and configured secret reference only where required; Expected channel result = In-app item, email/message file, browser push or actual external attempt",Pulse → Channels & rules → Channel setup / Notification rules,"1. Open channel setup and inspect the offered type, state and configuration fields. 2. Create/save the isolated training configuration using permitted references. 3. Configure the rule’s registered event, recipient selection and approved content/link. 4. Complete the channel/rule’s offered review/lifecycle actions and inspect effective configuration. 5. Use a prepared eligible event and follow its actual channel result. 6. Inspect a prepared disabled/misconfigured route and restore only the approved training setting.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-PULSE-04,,Awaiting client execution,,,
KRN-FLOW-PULSE-05,Pulse,Pulse generation queue recovery versus Enterprise Scheduler recovery,,,,Request/job = Original Training Case Correspondence generation reference; State = Actual queued/running/failed/uncertain/ready result; Recovery scope = Small isolated permitted queue/job selection; Reason = Recover the original training producer request,Pulse → Requests & output / Delivery & operations → selected generation job and command history,"1. Open the original correspondence request and follow its generation job. 2. Inspect its current attempt, dependency state and offered recovery actions. 3. Check published content, current authorization and worker/queue readiness before retrying. 4. Use the permitted bounded recovery for the original producer reference. 5. Open command history and compare the original and recovery attempt/outcome. 6. If launched by Enterprise Scheduler, follow the parent run back to its linked producer result.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-PULSE-05,,Awaiting client execution,,,
KRN-FLOW-AXIS-01,Axis,Profile/locale-specific experience and restrictive overrides,,,,Version purpose = Training read-only locale variation; Profile / locale = An approved optional training profile scope / offered locale; Presentation = Approved label draft and restrictive read-only/visibility setting; Captured revision = Exact referenced label/source and experience revision,Axis → Experience Administration → Experience Versions → selected/new version,"1. Open the owning screen and inspect its current effective experience and dependencies. 2. Create a permitted experience draft and choose its eligible profile/locale scope. 3. Capture the intended approved label revision and restrictive field setting. 4. Save and preview using the current selected authorized context. 5. Complete responsible-owner confirmation and independent review through the offered owning record actions. 6. Publish through the supported action, inspect effective configuration and separately verify its rendering applicability.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-AXIS-01,,Awaiting client execution,,,
KRN-FLOW-AXIS-02,Axis,Rollback and the distinction between publication and activation,,,,Base = Earlier reviewed training experience version; New draft = Training rollback candidate; Reason = Restore the earlier approved training presentation values; Activation boundary = Experience configuration versus authored/generated screen publication,Axis → Experience Versions → selected earlier version → Copy Version for Rollback,"1. Inspect the current effective and intended earlier experience versions side by side. 2. Choose Copy Version for Rollback and save a new draft. 3. Review current source, label, profile/locale and permission dependencies. 4. Preview the copied candidate and obtain the required fresh owner/independent decisions. 5. Publish the approved candidate through its owning experience operation. 6. Inspect actual rendering/activation separately and return to the originating screen.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-AXIS-02,,Awaiting client execution,,,
KRN-FLOW-CUSTODIA-01,Custodia,Nested collection moves and inherited collection holds,,,,Parent / child = Training Evidence / Training Intake; Member = Admitted synthetic SYN-001 exact document version; Move = Place Training Intake under Training Evidence; Hold = Approved training collection-scoped hold on Training Evidence,Custodia → Collections → selected collection; Legal holds,1. Create or select the two owned training collections and add the permitted admitted version to the child. 2. Choose the parent/move action using current child and parent revisions. 3. Attempt a prepared reverse move that would create a cycle. 4. Place the permitted protective hold on the parent and inspect the child/document hold context. 5. Try the protected child detach or held member removal. 6. Complete the supported hold-release review and re-read current scope. 7. Repeat the originally intended permitted move/removal with fresh revisions.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-CUSTODIA-01,,Awaiting client execution,,,
KRN-FLOW-CUSTODIA-02,Custodia,Typed internal and external document relationships,,,,Source / target = SYN-001 v1 / SYN-002 v1; Relationship type = Offered approved training supporting-evidence type; External example = Owning application + object type + synthetic public UUID; Reason = Link the training supporting evidence,Custodia → Repository documents → selected version → Relationships,1. Open the current source version and inspect existing active links. 2. Choose the approved compatible relationship type and accessible exact target version. 3. Save and reopen the relationship from both permitted contexts. 4. Create the separate permitted external-reference example with its owner/object/public ID. 5. Try a prepared duplicate or hierarchy-cycle relationship. 6. Retire the permitted training relationship with reason and inspect history.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-CUSTODIA-02,,Awaiting client execution,,,
KRN-FLOW-CUSTODIA-03,Custodia,Private page notes independently of redaction,,,,Document/page = Admitted synthetic SYN-001 v1 / page 1; Private note = Training note: confirm the synthetic reference.; Comparison actors = The author and a different ordinary permitted viewer; Contrast = Separate exact-version redaction request,Custodia → document version → page viewer → private annotation,1. Open the permitted version/page and create a private note at the offered location. 2. Close and reopen the viewer as the author. 3. Open the same document as the different permitted viewer. 4. Compare the original document checksum and business-review state. 5. Update or retire the note through the offered current-revision action. 6. Open a separate reviewed rectangle-mask example and explain the difference.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-CUSTODIA-03,,Awaiting client execution,,,
KRN-FLOW-CUSTODIA-04,Custodia,Encrypted supporting-copy creation and integrity verification,,,,Source = Permitted admitted synthetic supporting document; Storage/copy configuration = Offered approved storage reference and copy settings; Reason = Verify the training supporting-copy custody chain; Verification = Returned copy reference and integrity result,Custodia → supporting Document custody → selected file → Create encrypted copy / Verify encrypted copy,"1. Open the supporting document and inspect its current custody/admission state. 2. Choose Create encrypted copy and review the allowed storage/copy fields. 3. Submit the permitted action once and retain its receipt. 4. Open Verify encrypted copy for that exact returned reference. 5. Compare the actual integrity result with its expected checksum/custody reference. 6. Read the source and copy histories, then return to tenant evidence or its owning custody record.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-CUSTODIA-04,,Awaiting client execution,,,
KRN-FLOW-CUSTODIA-05,Custodia,Persisted storage investigations and scheduled reconciliation,,,,Observation = An authorized stable read-only training scan; Case = Prepared harmless non-document artifact observation where permitted; Review note = Training observation reviewed; refer to the permitted scan evidence.; Worker = Dedicated configured reconciliation worker and current heartbeat,Custodia → Processing operations → Storage scan history / Storage investigations,"1. Open scan history and inspect the selected observation’s tenant, timestamp and counts. 2. Follow its prepared investigation case and read the original/current observations. 3. Add a permitted operator review note against the current observed revision. 4. Read a prepared later complete scan that no longer observes the anomaly. 5. Read the prepared recurring observation and inspect the same case history. 6. Inspect the dedicated worker’s current health, last successful scan and bounded failure/backoff state through the permitted operator surface. 7. Explain the recovery boundary and preserve investigation evidence.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-CUSTODIA-05,,Awaiting client execution,,,
KRN-FLOW-CUSTODIA-06,Custodia,Multi-file/ZIP intake and format-specific partial recovery,,,,"Batch = Synthetic evidence.pdf, evidence.docx, evidence.tiff and evidence.txt; ZIP sample = training-packet.zip containing only permitted small synthetic files; Metadata = Approved training class and required SYN reference fields; Recovery sample = One prepared invalid or failed item among otherwise eligible files",Custodia → Upload document / Upload processing → prepared small batch,"1. Choose the approved class/template and inspect current per-file, batch and ZIP limits. 2. Select the small permitted format batch and submit once. 3. Inspect each PDF/image/text/office-format item through the supported admission/extraction path. 4. Submit the separate bounded ZIP fixture and inspect its declared entries/derived file lineage. 5. Inspect the prepared partial-failure batch and retain successful item receipts. 6. Use offered bounded recovery for failed eligible items only, then re-read admission/extraction results. 7. Search/view the admitted/indexed outputs as an authorized ordinary user.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-CUSTODIA-06,,Awaiting client execution,,,
KRN-FLOW-MEDES-01,MEDES,"Administration, status meanings and owner settings",,,,"Case = Training evidence exchange; Area = Offered status/scope reference area; User/access owner = IAM User Accounts / current assignments; Settings owners = Current tenant configuration, Custodia classes/templates, Pulse templates, Regulix policies and reporting where offered",MEDES → Administration → Status reference / User administration / Settings / Scope reference,"1. Open Status reference and select the case/document/work area. 2. Open Scope reference and inspect the current user’s permitted case/member boundaries. 3. Follow User administration as an authorized administrator and inspect the linked account/assignment. 4. Open MEDES Settings and follow one permitted configuration owner link. 5. Inspect current class/template, correspondence-provider and workflow/reporting prerequisites without changing operational values. 6. Return through Back to the original MEDES case and refresh its current context.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-MEDES-01,,Awaiting client execution,,,
KRN-FLOW-MEDES-02,MEDES,Fax-cover fields and exact reviewed transmission packet,,,,Case/member = Current Training evidence exchange case; Cover = Eligible published training fax cover and offered cover fields; Destination = Controlled authorized training fax destination only if a provider is configured; Attachments = Exact admitted authorized SYN-001/SYN-002 versions in intended order; Reason = Review the complete synthetic training decision packet,MEDES → Correspondence → selected training case → fax cover / packet,"1. Open the current case correspondence action and select eligible published letter/cover content. 2. Complete the offered cover fields and choose the permitted current recipient/destination. 3. Add exact authorized attachment versions and inspect their packet order. 4. Generate/preview the assembled cover, letter and attachments and check every page. 5. Have the eligible independent reviewer decide that exact packet. 6. If the selected target provider is ready, dispatch through the offered action and follow the original provider attempt. 7. Reconcile an uncertain reply before another send and read the case correspondence/archive history.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-MEDES-02,,Awaiting client execution,,,
KRN-FLOW-NEXORA-01,Nexora,"Discussion creation, replies and moderation",,,,"Learning record = Published Training Evidence Handling course; Message = How do I identify the current evidence version in the training example?; Reply = Open the admitted version and compare its retained reference.; Actors = Eligible learner, another permitted participant and authorized moderator",Nexora → Discussions → Start discussion / selected thread,"1. Open Discussions and filter by the prepared published course. 2. Choose Start discussion, select the learning record and enter the synthetic question. 3. Open the thread as another eligible participant and post the reply. 4. Read the thread as the original learner and inspect author/time information. 5. Use the offered hide/moderation action as the authorized moderator on a prepared message. 6. Inspect the learner’s course/assignment state and retained discussion context.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-NEXORA-01,,Awaiting client execution,,,
KRN-FLOW-NEXORA-02,Nexora,Policy authoring/attestation and competency/readiness modeling,,,,Code / title = TRAINING_EVIDENCE_POLICY / Training evidence handling policy; Version / owner = 1.0 / authorized training policy owner; Policy text = Use the current admitted evidence version and preserve the review trail.; Attestation = Required acknowledgement of the exact assigned policy version; Linked course = Published Training Evidence Handling,Nexora → Content studio → Policy; Policies & mappings,"1. Create the Policy record with title, description, owner, version and text. 2. Set the offered attestation and source/review information, then complete required content review/publication. 3. Map the policy through the eligible course’s supported policy selection and review/publish the affected learning. 4. Assign the published policy/course to the training learner and inspect the exact assigned version. 5. As the learner, read and explicitly acknowledge the required policy where offered. 6. Prepare a controlled policy successor and inspect Coverage & change impact. 7. Revise/review the intended affected learning before adopting the successor.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-NEXORA-02,,Awaiting client execution,,,
KRN-FLOW-NEXORA-03,Nexora,Policy authoring/attestation and competency/readiness modeling,,,,Competencies = Training evidence identification / Training evidence review; Readiness model = TRAINING_EVIDENCE_READINESS; Factors = Identification weight 3; Review weight 1; Threshold = 80%; Learner evidence = Prepared assigned/completed and incomplete learning records,Nexora → Content studio → Competency / Readiness model; Competencies & readiness,"1. Author the two competency records and select their current eligible included courses. 2. Complete their required review/publication before selecting them in the readiness model. 3. Create the readiness model, choose the two competencies and enter weights 3 and 1 plus threshold 80. 4. Review/publish the model through the current content governance flow. 5. Open Readiness & skills for the permitted training population. 6. Compare the displayed result with current included-course completion and factor definitions. 7. Complete a separate legitimate learning obligation and refresh its result/history.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-NEXORA-02,,Awaiting client execution,,,
KRN-FLOW-NEXORA-04,Nexora,"Governed evidence-package request, approval, download and revocation",,,,"Evidence source = ASSIGNMENTS; repeat separately for ATTEMPTS, CREDENTIALS or AUDIT; Approved purpose = Existing independently approved IAM access purpose; UTC period / maximum = Prepared one-day training period / 100 records; Business reason = Review the synthetic training learning outcome evidence.; Reviewer/download = Different eligible compliance reviewer; requester download within seven days of approval",Nexora → Evidence & audit → Evidence packages,"1. Open Evidence packages and choose Request evidence package. 2. Select the source, approved purpose, UTC date range, record cap and reason. 3. Submit and reopen the pending request as its requester. 4. As the separate eligible compliance reviewer, inspect the exact scope/reason and approve or reject through the request. 5. As the requester, download the approved package within its seven-day window. 6. Inspect permitted recorded outcomes/activity and verify private notes and answer keys are excluded. 7. Revoke a separate prepared approved request as the eligible reviewer, then retry requester download.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-NEXORA-03,,Awaiting client execution,,,
KRN-FLOW-NEXORA-05,Nexora,"Learning administration, FAQ and announcements",,,,"Organization/support text = Training learning workspace / Contact the assigned training instructor.; Default due days = 14; Reminder lead days = 3; Time zone = UTC; Provider status = Current SCORM host, AI mentor and live-meeting readiness",Nexora → Learning administration,"1. Open Learning administration with the permitted administration capability. 2. Record the existing defaults before changing the isolated training setting. 3. Enter due days 14, reminder days 3, UTC and the synthetic support text. 4. Save with the current revision, reopen and compare values. 5. Inspect Learning service health and current pending-renewal/readiness results. 6. Read the SCORM/mentor/live-provider notices and follow only authorized platform owner links. 7. Restore the intended training configuration through another explicit saved change where required.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-NEXORA-04,,Awaiting client execution,,,
KRN-FLOW-NEXORA-06,Nexora,"Learning administration, FAQ and announcements",,,,FAQ code / question = TRAINING_CURRENT_EVIDENCE / How do I identify the current training evidence?; Answer = Open the admitted version and compare its retained version reference.; Announcement = TRAINING_REVIEW_NOTICE / Training review guidance is available.; Audience / period = Eligible training profile and offered effective bounds,Nexora → Content studio → Frequently asked question / Announcement; Learning help / Learning home,"1. Create and save the FAQ with question/title, description, category and answer. 2. Complete the required review/publication for that exact FAQ revision. 3. Open Learning help as an eligible learner and find the published question/answer. 4. Create the separate training announcement with body and eligible audience/effectivity. 5. Review/publish and inspect its appearance on the permitted Learning home. 6. Revise or retire the prepared content through its supported lifecycle and refresh the learner view.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-NEXORA-04,,Awaiting client execution,,,
KRN-FLOW-NEXORA-07,Nexora,"Learner saved content, ratings, notes and intelligence views",,,,"Course = Published Training Evidence Handling; Personal actions = Save/bookmark, offered rating and private note; Note = Training note: review the current evidence reference.; Report scope = Permitted training population, course/domain and offered period filters",Nexora → Course catalog / selected published course; Learning intelligence,"1. Open the published course as the ordinary permitted learner. 2. Use the offered save/bookmark action and record a permitted rating. 3. Save the private training note, leave the record and reopen it as the same learner. 4. Compare another eligible participant’s view of that course. 5. Inspect required lessons/assessment/attestation state. 6. Open Learning intelligence as an authorized reporter and apply the offered course/domain/population filters. 7. Use the separately governed evidence-package journey for a disclosure export.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-NEXORA-05,,Awaiting client execution,,,
KRN-FLOW-REGULIX-01,Regulix,"Timer wait, due-time advancement and repeated polling",,,,Definition = Prepared approved training model containing one supported timer wait; Business key = TRAINING_TIMER_01; Timer due = A short permitted future instant in the model’s supported zone/contract; Actors = Authorized starter and actual configured timer-service identity,Regulix → approved process/case definition → native runtime instance; timer-service operations,"1. Inspect the approved timer-bound training definition and its current permitted runtime binding. 2. Start the isolated instance once and retain its native ID/business key/checkpoint. 3. Inspect before the actual due instant. 4. After the due instant, inspect the actual configured timer-service claim/advancement result. 5. Repeat the permitted status/poll/reconciliation path for that same timer. 6. Inspect a prepared stale/denied timer action and retain its actual response. 7. Follow the resulting next node/task and owner history.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-REGULIX-01,,Awaiting client execution,,,
KRN-FLOW-REGULIX-02,Regulix,Claim/delegate/release and per-stage task eligibility,,,,Task = Prepared current training human-review task; Stage policy = Approved per-stage assignment policy and eligible candidates; Actors = Eligible Worker A and eligible Worker B; prepared unauthorized comparison user; Reason = Transfer the isolated training review duty,Regulix → Work Queue / selected native process or case task → assignment actions,"1. Open the current work queue as eligible Worker A and inspect the task’s assignment policy/stage. 2. Claim the selected task with its current owner/version fence. 3. Attempt a competing claim as the prepared other participant. 4. Use the task’s offered eligible delegate/reassign or release action with reason. 5. Open as eligible Worker B and inspect current assignment before completing. 6. Complete only the intended task and follow the persisted next stage. 7. Read the original claim, transfer and completion history.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-REGULIX-02,,Awaiting client execution,,,
KRN-FLOW-REGULIX-03,Regulix,Current-context and decision/event-driven CMMN sentries,,,,Case model = Prepared training case with explicit supported entry/exit sentries; Context sentry = CTX_EQUALS; ctxPath review.status; matchValues APPROVED; Decision sentry = DMN_MATCH with approved plan/model UUID/hash pins; Event sentry = EVENT_FIRED with approved eventId/scopeId and the prepared correlation key; Replay = Original update/event request identity and expected checkpoint,Regulix → CMMN Design / approved native case → variables and event actions,1. Inspect the approved case’s supported entry/exit sentry clauses and actual pinned dependencies. 2. Start once with a prepared nonmatching review.status value. 3. Patch current variables through the supported versioned action and settle. 4. Inspect the pinned decision evaluation and its recorded output when applicable. 5. Correlate the exact prepared event/scope/key through the supported action. 6. Replay the same request and inspect the retained checkpoint/occurrence result. 7. Complete the newly eligible assigned work and inspect case history.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-REGULIX-03,,Awaiting client execution,,,
KRN-FLOW-REGULIX-04,Regulix,Incident investigation and closure,,,,"Incident = Prepared open training incident and its originating obligation; Evidence = Actual warning/breach timing, task/instance and policy references; Closure reason = Training issue investigated and permitted recovery recorded.; Comparison = Original OPEN event and retained CLOSE history",Regulix → Incident Log / SLA Incidents → selected OPEN incident,"1. Filter the permitted incident list to the prepared training obligation and open its latest current record. 2. Read measured timing, evidence and any current owner recovery state. 3. Verify current close eligibility and enter the meaningful closure reason. 4. Submit once through the native close operation. 5. Reopen history and inspect the retained OPEN/CLOSE events and elapsed information. 6. Open the originating business record and compare its actual state.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-REGULIX-04,,Awaiting client execution,,,
KRN-FLOW-REGULIX-05,Regulix,Loop and manually activated multi-instance process work,,,,Node = Graph-owned manualActivation multi-instance node; Instance = Prepared native training UUID and expected checkpoint version; Participants/items = Small permitted prepared set from the model’s actual input contract; Completion = Assigned child task and graph completion rule,Regulix → approved BPMN model → selected native instance → supported multi-instance action,1. Inspect the approved model’s multi-instance node and supported activation/completion contract. 2. Start or select the prepared native instance at that node and inspect the checkpoint. 3. Submit the supported manual activation for the intended small item set. 4. Open child tasks as their currently eligible participants. 5. Complete the assigned children through their supported owner actions. 6. Inspect parent continuation and replay/stale action behavior.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-REGULIX-05,,Awaiting client execution,,,
KRN-FLOW-REGULIX-06,Regulix,Loop and manually activated multi-instance process work,,,,Model = Prepared approved bounded loop example; Facts = Prepared continue and finish values from the model’s typed contract; Task owner = Current assigned eligible worker; Checkpoint = Current native instance version for each iteration,Regulix → approved BPMN training loop → assigned task,"1. Inspect the model’s loop node, continuation rule and safe training bound. 2. Start once and open the current assigned loop task. 3. Complete it using the prepared continue fact through the supported task action. 4. Inspect the next task and current checkpoint before acting again. 5. Supply the prepared finish fact and complete as the current eligible assignee. 6. Read iteration/task history and inspect replay or unauthorized completion denial.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-REGULIX-05,,Awaiting client execution,,,
KRN-FLOW-REGULIX-07,Regulix,Simulation/process suites and terminal instance archive,,,,Definition = Prepared approved model with required native/source alias binding where applicable; Scenario A/B = Prepared normal and denied/default facts from the exact model; Test records = Supported process-test drafts and current scenario references; Side effects = Isolated/ephemeral supported simulation execution,Regulix → approved design/definition → supported simulation or process test suite,"1. Inspect the selected model and the actual supported simulation/test-suite action. 2. Prepare the two explicit scenarios and expected node/decision outcomes. 3. Run the supported simulation against the prepared isolated facts. 4. Inspect the execution trace and compare the expected path/state with the actual result. 5. Where configured, run the supported suite using its current test drafts/verified definition binding. 6. Verify the result scope and retain reports without claiming live business or external effects.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-REGULIX-06,,Awaiting client execution,,,
KRN-FLOW-REGULIX-08,Regulix,Simulation/process suites and terminal instance archive,,,,"Instance = Prepared terminal native process or case UUID; Version = Current expected checkpoint/record version; Reason = Archive the completed synthetic training instance; History = Retained engine state, audit and original archive receipt",Regulix → native process/case instances → terminal training instance → Archive,1. Open the terminal training instance and retain its final state and checkpoint. 2. Confirm that its supported archive action is eligible and record the reason. 3. Submit the archive command once through the native owner. 4. Refresh ordinary lists and inspect the supported retained audit/archive evidence. 5. Reconcile/replay the exact original archive request through its supported idempotent path. 6. Inspect a prepared ineligible active/foreign-scope archive attempt.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-REGULIX-06,,Awaiting client execution,,,
KRN-FLOW-TENANT-01,Tenant Engine,Separate parent-relationship and branding change walkthroughs,,,,Child / parent = TRAINING_TENANT / prepared authorized TRAINING_PARENT; Relationship = Offered parent relationship and intended permitted period; Reason = Establish the isolated training parent relationship; End change = Separate governed relationship-end proposal,Tenant Engine → Tenant operations → selected tenant → Propose tenant parent / relationship end,1. Inspect both tenant identities and existing relationships before proposing a new one. 2. Open Propose tenant parent and select the eligible parent/period with reason. 3. Submit and inspect the pending state before review. 4. Have the eligible independent reviewer decide the exact owning change. 5. Read the current relationship tree and both tenant histories. 6. Create and independently decide the separate relationship-end proposal where permitted.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-TENANT-01,,Awaiting client execution,,,
KRN-FLOW-TENANT-02,Tenant Engine,Separate parent-relationship and branding change walkthroughs,,,,Tenant = TRAINING_TENANT; Branding values = Training workspace display name and approved offered theme/logo references; Reason = Review the training tenant presentation change; Restore = Earlier intended training branding as a new governed change,Tenant Engine → Tenant operations → selected tenant → Propose tenant branding / Branding preview,"1. Read the tenant’s current published branding and retain the intended restore values. 2. Open Propose tenant branding and enter the permitted synthetic display/asset values. 3. Use the offered preview and inspect title/theme/logo behavior at supported sizes. 4. Submit and have the eligible independent reviewer decide the exact change. 5. Open published branding/preview again and verify actual effective adoption. 6. Where needed, submit/review the intended restore values as another controlled proposal.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-TENANT-01,,Awaiting client execution,,,
KRN-FLOW-TENANT-03,Tenant Engine,Custodia supporting evidence through tenant identity review,,,,Onboarding case = Current TRAINING_TENANT request; Supporting file = Synthetic identity-evidence.pdf under an approved training class; Custody reference = Returned exact document/version/hash; Identity evidence = Offered evidence type and meaningful training reason,Tenant Engine → onboarding case → supporting Document custody → Identity evidence review,1. Open the onboarding case and its identity owner-step requirement. 2. Upload the permitted synthetic supporting file through the offered custody action. 3. Follow actual quarantine/scan/admission processing and inspect the exact usable version/hash. 4. Capture the supported identity evidence using that admitted custody reference. 5. Have the eligible independent reviewer decide the evidence on its owning record. 6. Run the current identity/owner readiness check and inspect the result. 7. Use the permitted revocation/current-invalidity example and rerun readiness.,"Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-TENANT-02,,Awaiting client execution,,,
KRN-FLOW-CORE-01,Kernel Core,Generic active/inactive lifecycle with explicit false retained,,,,Record = Disposable TRAINING_LIFECYCLE master entry; Default example = Omit active only where the current create contract defines a default; Explicit example = is_active=false through the offered control/contract; Unrelated edit = Change training description only; History/restore = Include inactive; explicit permitted restoration,Core / relevant owner master → prepared disposable record → active/inactive controls,"1. Inspect the selected owner’s create/update/lifecycle rules and current active field control. 2. Create the disposable default example and read back the stored active state. 3. Create or change the separate prepared record with is_active=false, expressed as unchecked Active in the offered control. 4. Edit only its description through the ordinary update form and reopen it. 5. Compare ordinary current choices with Include inactive and historical/linked readback. 6. Use only the explicit permitted restore/reactivate action where offered and inspect its history. 7. Inspect a prepared blocked dependency or protected-state attempt.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-LIFECYCLE-01,,Awaiting client execution,,,
KRN-FLOW-SUPPORTING-01,Supporting Asset Operations,"Supporting Asset Operations: request, decide, allocate and acknowledge",,,,"Application = Configured Asset Operations entry and authorized application profile; Inventory item = Prepared available training equipment item; Request = Small isolated training request with business reason; Actors = Requester, eligible decision-maker, allocator and intended recipient; Alternative requests = Separate prepared reject/cancel examples",Supporting Asset Operations application → Inventory / Request queue / Activity history,"1. Open the configured supporting application and inspect its permitted equipment inventory. 2. Choose Request equipment and submit the intended item/quantity/reason through its actual offered fields. 3. As the eligible reviewer, open and approve the intended training request. 4. As the eligible allocator, allocate the permitted available training item and inspect readback. 5. As the intended recipient, acknowledge receipt through the supported action. 6. Use separate prepared requests to demonstrate permitted rejection and cancellation before incompatible terminal states. 7. Open Activity history and the permitted inventory/request reports. 8. Return to the Kernel documentation crosswalk and distinguish supporting application scope from Nexora learning.","Retain the prepared input, current selected context, exact record/version, permitted and denied outcomes and the final owner history. Record actual results separately from these expected outcomes.",FLOW-E-SCOPE-01,,Awaiting client execution,,,