From 726ff50101ed6d4f4bd457c67df2dd0638a1a482 Mon Sep 17 00:00:00 2001 From: Marjukka Niinioja Date: Wed, 5 Aug 2026 14:15:34 +0300 Subject: [PATCH 1/3] fixed station ids, removed and simplified canvases --- src/data/canvas/canvasData.json | 1933 ++------ src/data/canvas/localizedData.json | 5143 ++++++--------------- src/data/method/cycles.json | 151 +- src/data/method/de/labels.cycles.json | 24 +- src/data/method/de/labels.resources.json | 290 +- src/data/method/en/labels.cycles.json | 24 +- src/data/method/en/labels.resources.json | 290 +- src/data/method/fi/labels.cycles.json | 24 +- src/data/method/fi/labels.resources.json | 306 +- src/data/method/fr/labels.cycles.json | 24 +- src/data/method/fr/labels.resources.json | 304 +- src/data/method/lines.json | 40 +- src/data/method/pt/labels.cycles.json | 24 +- src/data/method/pt/labels.resources.json | 306 +- src/data/method/resources.json | 26 - src/data/method/station-stakeholders.json | 42 +- 16 files changed, 2615 insertions(+), 6336 deletions(-) diff --git a/src/data/canvas/canvasData.json b/src/data/canvas/canvasData.json index 9dfa753..c0a1b1a 100644 --- a/src/data/canvas/canvasData.json +++ b/src/data/canvas/canvasData.json @@ -351,7 +351,7 @@ "id": "customerJourneyCanvas", "layout": { "columns": 5, - "rows": 4 + "rows": 5 }, "metadata": { "source": "APIOps Cycles", @@ -443,6 +443,16 @@ "rowSpan": 1 }, "fillOrder": 8 + }, + { + "id": "improvementOpportunities", + "gridPosition": { + "column": 0, + "row": 4, + "colSpan": 5, + "rowSpan": 1 + }, + "fillOrder": 9 } ] }, @@ -1312,7 +1322,7 @@ "highlight": true }, { - "id": "supportingEvidence", + "id": "reusedEvidence", "gridPosition": { "column": 2, "row": 0, @@ -1322,65 +1332,43 @@ "fillOrder": 2 }, { - "id": "automationScope", + "id": "criticalAssumptions", "gridPosition": { "column": 0, "row": 1, - "colSpan": 1, + "colSpan": 2, "rowSpan": 1 }, "fillOrder": 3 }, { - "id": "responsibilityAndSolutionHypothesis", - "gridPosition": { - "column": 1, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4, - "highlight": true - }, - { - "id": "criticalAssumptions", + "id": "validationExperiment", "gridPosition": { "column": 2, "row": 1, "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 5, - "highlight": true - }, - { - "id": "validationExperiment", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 2, - "rowSpan": 1 - }, - "fillOrder": 6, + "fillOrder": 4, "highlight": true }, { "id": "decision", "gridPosition": { - "column": 2, + "column": 0, "row": 2, - "colSpan": 2, + "colSpan": 4, "rowSpan": 1 }, - "fillOrder": 7, + "fillOrder": 5, "highlight": true } ] }, - "humanAutomationResponsibilityCanvas": { - "id": "humanAutomationResponsibilityCanvas", + "automationWorkflowCanvas": { + "id": "automationWorkflowCanvas", "layout": { - "columns": 3, + "columns": 6, "rows": 3 }, "metadata": { @@ -1393,105 +1381,74 @@ }, "sections": [ { - "id": "processStep", + "id": "selectedCustomerCapabilityOutcomes", "gridPosition": { "column": 0, "row": 0, - "colSpan": 1, + "colSpan": 6, "rowSpan": 1 }, "fillOrder": 1, - "highlight": true, - "journeySteps": true - }, - { - "id": "humanResponsibility", - "gridPosition": { - "column": 1, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 2 - }, - { - "id": "ruleOrWorkflowResponsibility", - "gridPosition": { - "column": 2, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 3 + "highlight": true }, { - "id": "agentOrAiResponsibility", + "id": "internalWorkflowSteps", "gridPosition": { "column": 0, "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4 - }, - { - "id": "apiOrSystemResponsibility", - "gridPosition": { - "column": 1, - "row": 1, - "colSpan": 1, + "colSpan": 4, "rowSpan": 1 }, - "fillOrder": 5 + "fillOrder": 2, + "journeySteps": true }, { - "id": "rpaOrUiAutomationResponsibility", + "id": "workAllocationHumanControl", "gridPosition": { - "column": 2, + "column": 4, "row": 1, - "colSpan": 1, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 6 + "fillOrder": 3 }, { - "id": "requiredOversight", + "id": "inputsOutputsInteractions", "gridPosition": { "column": 0, "row": 2, - "colSpan": 1, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 7, - "highlight": true + "fillOrder": 4 }, { - "id": "escalation", + "id": "decisionsExceptionsRecovery", "gridPosition": { - "column": 1, + "column": 2, "row": 2, - "colSpan": 1, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 8 + "fillOrder": 5 }, { - "id": "evidenceOrAuditTrail", + "id": "evidenceMonitoring", "gridPosition": { - "column": 2, + "column": 4, "row": 2, - "colSpan": 1, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 9 + "fillOrder": 6 } ] }, - "automationWorkflowCanvas": { - "id": "automationWorkflowCanvas", + "automationArchitectureDecisionCanvas": { + "id": "automationArchitectureDecisionCanvas", "layout": { - "columns": 5, - "rows": 3 + "columns": 4, + "rows": 2 }, "metadata": { "source": "APIOps Cycles", @@ -1503,7 +1460,7 @@ }, "sections": [ { - "id": "trigger", + "id": "reusedInputs", "gridPosition": { "column": 0, "row": 0, @@ -1514,154 +1471,212 @@ "highlight": true }, { - "id": "inputs", + "id": "viableOptions", "gridPosition": { "column": 1, "row": 0, - "colSpan": 1, + "colSpan": 2, "rowSpan": 1 }, "fillOrder": 2 }, { - "id": "workflowStages", + "id": "selectedApproach", "gridPosition": { - "column": 2, + "column": 3, "row": 0, "colSpan": 1, - "rowSpan": 1 + "rowSpan": 2 }, "fillOrder": 3, - "journeySteps": true + "highlight": true }, { - "id": "decisionsAndRules", + "id": "decisionRationale", "gridPosition": { - "column": 3, - "row": 0, + "column": 0, + "row": 1, "colSpan": 1, "rowSpan": 1 }, "fillOrder": 4 }, { - "id": "agentActions", + "id": "rejectedAlternatives", "gridPosition": { - "column": 4, - "row": 0, + "column": 1, + "row": 1, "colSpan": 1, "rowSpan": 1 }, "fillOrder": 5 }, { - "id": "systemInteractions", + "id": "openRisks", "gridPosition": { - "column": 0, + "column": 2, "row": 1, "colSpan": 1, "rowSpan": 1 }, "fillOrder": 6 + } + ] + }, + "automationReadinessOperationsCanvas": { + "id": "automationReadinessOperationsCanvas", + "layout": { + "columns": 3, + "rows": 2 + }, + "metadata": { + "source": "APIOps Cycles", + "license": "CC-BY-SA 4.0", + "authors": [ + "Osaango Ltd" + ], + "website": "www.apiopscycles.com" + }, + "sections": [ + { + "id": "ownership", + "gridPosition": { + "column": 0, + "row": 0, + "colSpan": 1, + "rowSpan": 1 + }, + "fillOrder": 1, + "highlight": true }, { - "id": "dataSources", + "id": "environmentsAndAccess", "gridPosition": { "column": 1, - "row": 1, + "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 7 + "fillOrder": 2 }, { - "id": "humanTasks", + "id": "testEvidence", "gridPosition": { "column": 2, + "row": 0, + "colSpan": 1, + "rowSpan": 1 + }, + "fillOrder": 3 + }, + { + "id": "monitoringAndSupport", + "gridPosition": { + "column": 0, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 8 + "fillOrder": 4 }, { - "id": "handoffs", + "id": "failureAndRecovery", "gridPosition": { - "column": 3, + "column": 1, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 9 + "fillOrder": 5 }, { - "id": "exceptions", + "id": "documentationRisksAndReadiness", "gridPosition": { - "column": 4, + "column": 2, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 10, + "fillOrder": 6, "highlight": true - }, + } + ] + }, + "integrationCapabilityHypothesisCanvas": { + "id": "integrationCapabilityHypothesisCanvas", + "layout": { + "columns": 4, + "rows": 3 + }, + "metadata": { + "source": "APIOps Cycles", + "license": "CC-BY-SA 4.0", + "authors": [ + "Osaango Ltd" + ], + "website": "www.apiopscycles.com" + }, + "sections": [ { - "id": "retriesAndTimeouts", + "id": "capabilityToValidate", "gridPosition": { "column": 0, - "row": 2, - "colSpan": 1, + "row": 0, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 11 + "fillOrder": 1, + "highlight": true }, { - "id": "outputs", + "id": "reusedEvidence", "gridPosition": { - "column": 1, - "row": 2, - "colSpan": 1, + "column": 2, + "row": 0, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 12 + "fillOrder": 2 }, { - "id": "auditEvidence", + "id": "criticalAssumptions", "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 1, + "column": 0, + "row": 1, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 13 + "fillOrder": 3 }, { - "id": "monitoringPoints", + "id": "validationStep", "gridPosition": { - "column": 3, - "row": 2, - "colSpan": 1, + "column": 2, + "row": 1, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 14 + "fillOrder": 4, + "highlight": true }, { - "id": "recoveryPath", + "id": "decision", "gridPosition": { - "column": 4, + "column": 0, "row": 2, - "colSpan": 1, + "colSpan": 4, "rowSpan": 1 }, - "fillOrder": 15 + "fillOrder": 5, + "highlight": true } ] }, - "automationArchitectureDecisionCanvas": { - "id": "automationArchitectureDecisionCanvas", + "integrationConsumerProviderRequirementsCanvas": { + "id": "integrationConsumerProviderRequirementsCanvas", "layout": { - "columns": 5, - "rows": 4 + "columns": 3, + "rows": 2 }, "metadata": { "source": "APIOps Cycles", @@ -1673,17 +1688,18 @@ }, "sections": [ { - "id": "nativeFeature", + "id": "selectedPartiesAndUseCases", "gridPosition": { "column": 0, "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 1 + "fillOrder": 1, + "highlight": true }, { - "id": "workflow", + "id": "providerCommitments", "gridPosition": { "column": 1, "row": 0, @@ -1693,7 +1709,7 @@ "fillOrder": 2 }, { - "id": "rule", + "id": "consumerCommitments", "gridPosition": { "column": 2, "row": 0, @@ -1703,154 +1719,121 @@ "fillOrder": 3 }, { - "id": "agent", + "id": "accessAndValidationAgreement", "gridPosition": { - "column": 3, - "row": 0, + "column": 0, + "row": 1, "colSpan": 1, "rowSpan": 1 }, "fillOrder": 4 }, { - "id": "connector", - "gridPosition": { - "column": 4, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 5 - }, - { - "id": "api", - "gridPosition": { - "column": 0, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 6 - }, - { - "id": "event", + "id": "failureAndRecoveryAgreement", "gridPosition": { "column": 1, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 7 + "fillOrder": 5 }, { - "id": "customCode", + "id": "changeAndLifecycleAgreement", "gridPosition": { "column": 2, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 8 - }, - { - "id": "rpa", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 9 - }, - { - "id": "humanTask", - "gridPosition": { - "column": 4, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 10 - }, + "fillOrder": 6 + } + ] + }, + "integrationArchitectureDecisionCanvas": { + "id": "integrationArchitectureDecisionCanvas", + "layout": { + "columns": 4, + "rows": 2 + }, + "metadata": { + "source": "APIOps Cycles", + "license": "CC-BY-SA 4.0", + "authors": [ + "Osaango Ltd" + ], + "website": "www.apiopscycles.com" + }, + "sections": [ { - "id": "feasibilityReliabilitySecurity", + "id": "reusedInputs", "gridPosition": { "column": 0, - "row": 2, + "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 11, + "fillOrder": 1, "highlight": true }, { - "id": "maintainabilityScalabilityCost", + "id": "viableOptions", "gridPosition": { "column": 1, - "row": 2, - "colSpan": 1, + "row": 0, + "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 12 + "fillOrder": 2 }, { - "id": "latencyObservabilityRecoverability", + "id": "selectedApproach", "gridPosition": { - "column": 2, - "row": 2, + "column": 3, + "row": 0, "colSpan": 1, - "rowSpan": 1 + "rowSpan": 2 }, - "fillOrder": 13 + "fillOrder": 3, + "highlight": true }, { - "id": "skillsVendorFit", + "id": "decisionRationale", "gridPosition": { - "column": 3, - "row": 2, + "column": 0, + "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 14 + "fillOrder": 4 }, { - "id": "recommendedHybridApproach", + "id": "rejectedAlternatives", "gridPosition": { - "column": 4, - "row": 2, + "column": 1, + "row": 1, "colSpan": 1, - "rowSpan": 2 - }, - "fillOrder": 15, - "highlight": true - }, - { - "id": "decisionRationale", - "gridPosition": { - "column": 0, - "row": 3, - "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 16 + "fillOrder": 5 }, { - "id": "openQuestionsAndRisks", + "id": "openRisks", "gridPosition": { "column": 2, - "row": 3, - "colSpan": 2, + "row": 1, + "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 17 + "fillOrder": 6 } ] }, - "automationReadinessOperationsCanvas": { - "id": "automationReadinessOperationsCanvas", + "integrationReadinessOperationsCanvas": { + "id": "integrationReadinessOperationsCanvas", "layout": { - "columns": 4, - "rows": 4 + "columns": 3, + "rows": 2 }, "metadata": { "source": "APIOps Cycles", @@ -1862,17 +1845,18 @@ }, "sections": [ { - "id": "businessOwner", + "id": "ownership", "gridPosition": { "column": 0, "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 1 + "fillOrder": 1, + "highlight": true }, { - "id": "operationalOwner", + "id": "environmentsAndAccess", "gridPosition": { "column": 1, "row": 0, @@ -1882,7 +1866,7 @@ "fillOrder": 2 }, { - "id": "users", + "id": "testEvidence", "gridPosition": { "column": 2, "row": 0, @@ -1892,141 +1876,118 @@ "fillOrder": 3 }, { - "id": "permissions", - "gridPosition": { - "column": 3, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4 - }, - { - "id": "credentials", + "id": "monitoringAndSupport", "gridPosition": { "column": 0, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 5 + "fillOrder": 4 }, { - "id": "environments", + "id": "failureAndRecovery", "gridPosition": { "column": 1, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 6 + "fillOrder": 5 }, { - "id": "testEvidence", + "id": "documentationRisksAndReadiness", "gridPosition": { "column": 2, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 7, + "fillOrder": 6, "highlight": true - }, - { - "id": "exceptionHandling", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8 - }, + } + ] + }, + "integrationSolutionDesignCanvas": { + "id": "integrationSolutionDesignCanvas", + "layout": { + "columns": 3, + "rows": 2 + }, + "metadata": { + "source": "APIOps Cycles", + "license": "CC-BY-SA 4.0", + "authors": [ + "Osaango Ltd" + ], + "website": "www.apiopscycles.com" + }, + "sections": [ { - "id": "monitoring", + "id": "selectedInputs", "gridPosition": { "column": 0, - "row": 2, + "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 9 + "fillOrder": 1, + "highlight": true }, { - "id": "support", + "id": "contractAndModel", "gridPosition": { "column": 1, - "row": 2, + "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 10 + "fillOrder": 2 }, { - "id": "manualFallback", + "id": "mappingAndDelivery", "gridPosition": { "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11 - }, - { - "id": "rollback", - "gridPosition": { - "column": 3, - "row": 2, + "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 12 + "fillOrder": 3 }, { - "id": "documentation", + "id": "errorsAndRecovery", "gridPosition": { "column": 0, - "row": 3, + "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 13 + "fillOrder": 4 }, { - "id": "deploymentDecision", + "id": "securityAndTrust", "gridPosition": { "column": 1, - "row": 3, + "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 14, - "highlight": true + "fillOrder": 5 }, { - "id": "knownRisks", + "id": "observabilityAndEvolution", "gridPosition": { "column": 2, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 15 - }, - { - "id": "improvementBacklog", - "gridPosition": { - "column": 3, - "row": 3, + "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 16 + "fillOrder": 6 } ] }, - "integrationCapabilityHypothesisCanvas": { - "id": "integrationCapabilityHypothesisCanvas", + "capabilityHypothesisCanvas": { + "id": "capabilityHypothesisCanvas", "layout": { "columns": 4, "rows": 3 @@ -2041,7 +2002,7 @@ }, "sections": [ { - "id": "hypothesis", + "id": "capabilityToValidate", "gridPosition": { "column": 0, "row": 0, @@ -2052,7 +2013,7 @@ "highlight": true }, { - "id": "consumersAndReuseScope", + "id": "reusedEvidence", "gridPosition": { "column": 2, "row": 0, @@ -2062,75 +2023,44 @@ "fillOrder": 2 }, { - "id": "providerAndOwner", + "id": "criticalAssumptions", "gridPosition": { "column": 0, "row": 1, - "colSpan": 1, + "colSpan": 2, "rowSpan": 1 }, "fillOrder": 3 }, { - "id": "supportingEvidence", - "gridPosition": { - "column": 1, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4 - }, - { - "id": "implementationStyleHypothesis", + "id": "minimumValidation", "gridPosition": { "column": 2, "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 5 - }, - { - "id": "criticalAssumptions", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 6, - "highlight": true - }, - { - "id": "validationExperiment", - "gridPosition": { - "column": 0, - "row": 2, "colSpan": 2, "rowSpan": 1 }, - "fillOrder": 7, + "fillOrder": 4, "highlight": true }, { "id": "decision", "gridPosition": { - "column": 2, + "column": 0, "row": 2, - "colSpan": 2, + "colSpan": 4, "rowSpan": 1 }, - "fillOrder": 8, + "fillOrder": 5, "highlight": true } ] }, - "integrationConsumerProviderRequirementsCanvas": { - "id": "integrationConsumerProviderRequirementsCanvas", + "capabilityConsumerProducerRequirementsCanvas": { + "id": "capabilityConsumerProducerRequirementsCanvas", "layout": { - "columns": 4, - "rows": 3 + "columns": 3, + "rows": 2 }, "metadata": { "source": "APIOps Cycles", @@ -2142,7 +2072,7 @@ }, "sections": [ { - "id": "consumerSystemsAndTeams", + "id": "selectedConsumersAndUseCases", "gridPosition": { "column": 0, "row": 0, @@ -2153,28 +2083,27 @@ "highlight": true }, { - "id": "providerResponsibilities", + "id": "ownerAndProducerCommitments", "gridPosition": { "column": 1, "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 2, - "highlight": true + "fillOrder": 2 }, { - "id": "interactionAndDataNeeds", + "id": "consumerResponsibilities", "gridPosition": { "column": 2, "row": 0, - "colSpan": 2, + "colSpan": 1, "rowSpan": 1 }, "fillOrder": 3 }, { - "id": "onboardingAndAccess", + "id": "accessAndOnboardingAgreement", "gridPosition": { "column": 0, "row": 1, @@ -2184,7 +2113,7 @@ "fillOrder": 4 }, { - "id": "environmentsAndTestAccess", + "id": "serviceAndLifecycleAgreement", "gridPosition": { "column": 1, "row": 1, @@ -2194,7 +2123,7 @@ "fillOrder": 5 }, { - "id": "credentialsAndIdentity", + "id": "openCommitments", "gridPosition": { "column": 2, "row": 1, @@ -2202,64 +2131,14 @@ "rowSpan": 1 }, "fillOrder": 6 - }, - { - "id": "compatibilityAndVersioning", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 7 - }, - { - "id": "serviceExpectations", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8 - }, - { - "id": "dataQualityAndObservability", - "gridPosition": { - "column": 1, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 9 - }, - { - "id": "supportAndFailureHandling", - "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 10 - }, - { - "id": "replayReconciliationRecovery", - "gridPosition": { - "column": 3, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11 } ] }, - "integrationArchitectureDecisionCanvas": { - "id": "integrationArchitectureDecisionCanvas", + "capabilityArchitectureDecisionCanvas": { + "id": "capabilityArchitectureDecisionCanvas", "layout": { "columns": 4, - "rows": 5 + "rows": 2 }, "metadata": { "source": "APIOps Cycles", @@ -2271,186 +2150,74 @@ }, "sections": [ { - "id": "synchronousApi", + "id": "reusedInputs", "gridPosition": { "column": 0, "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 1 + "fillOrder": 1, + "highlight": true }, { - "id": "eventDriven", + "id": "viableOptions", "gridPosition": { "column": 1, "row": 0, - "colSpan": 1, + "colSpan": 2, "rowSpan": 1 }, "fillOrder": 2 }, { - "id": "messagingQueue", - "gridPosition": { - "column": 2, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 3 - }, - { - "id": "batchFileExchange", + "id": "selectedApproach", "gridPosition": { "column": 3, "row": 0, "colSpan": 1, - "rowSpan": 1 + "rowSpan": 2 }, - "fillOrder": 4 + "fillOrder": 3, + "highlight": true }, { - "id": "stream", + "id": "decisionRationale", "gridPosition": { "column": 0, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 5 + "fillOrder": 4 }, { - "id": "etlElt", + "id": "rejectedAlternatives", "gridPosition": { "column": 1, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 6 + "fillOrder": 5 }, { - "id": "dataProduct", + "id": "openRisks", "gridPosition": { "column": 2, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 7 - }, - { - "id": "directDatabase", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8 - }, - { - "id": "sharedPlatform", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 9 - }, - { - "id": "pointToPoint", - "gridPosition": { - "column": 1, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 10 - }, - { - "id": "managedConnector", - "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11 - }, - { - "id": "customIntegration", - "gridPosition": { - "column": 3, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 12 - }, - { - "id": "hybridApproach", - "gridPosition": { - "column": 0, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 13 - }, - { - "id": "evaluationCriteria", - "gridPosition": { - "column": 1, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 14, - "highlight": true - }, - { - "id": "selectedStyleAndPlatform", - "gridPosition": { - "column": 2, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 15, - "highlight": true - }, - { - "id": "rationaleAndRejectedAlternatives", - "gridPosition": { - "column": 3, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 16, - "highlight": true - }, - { - "id": "openRisksAndAssumptions", - "gridPosition": { - "column": 0, - "row": 4, - "colSpan": 4, - "rowSpan": 1 - }, - "fillOrder": 17, - "highlight": true + "fillOrder": 6 } ] }, - "integrationReadinessOperationsCanvas": { - "id": "integrationReadinessOperationsCanvas", + "capabilitySolutionDesignCanvas": { + "id": "capabilitySolutionDesignCanvas", "layout": { - "columns": 4, - "rows": 5 + "columns": 3, + "rows": 2 }, "metadata": { "source": "APIOps Cycles", @@ -2462,7 +2229,7 @@ }, "sections": [ { - "id": "businessOwner", + "id": "selectedInputs", "gridPosition": { "column": 0, "row": 0, @@ -2473,1115 +2240,133 @@ "highlight": true }, { - "id": "integrationOwner", + "id": "boundaryAndInteraction", "gridPosition": { "column": 1, "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 2, - "highlight": true + "fillOrder": 2 }, { - "id": "producerOwners", + "id": "contractRulesAndOutcomes", "gridPosition": { "column": 2, "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 3, - "highlight": false - }, - { - "id": "consumerOwners", - "gridPosition": { - "column": 3, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4, - "highlight": false + "fillOrder": 3 }, { - "id": "platformOwner", + "id": "errorsAndSecurity", "gridPosition": { "column": 0, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 5, - "highlight": false + "fillOrder": 4 }, { - "id": "environments", + "id": "lifecycleAndSupport", "gridPosition": { "column": 1, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 6, - "highlight": false + "fillOrder": 5 }, { - "id": "credentials", + "id": "observability", "gridPosition": { "column": 2, "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 7, - "highlight": false - }, - { - "id": "deployment", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8, - "highlight": false - }, + "fillOrder": 6 + } + ] + }, + "capabilityReadinessOperationsCanvas": { + "id": "capabilityReadinessOperationsCanvas", + "layout": { + "columns": 3, + "rows": 2 + }, + "metadata": { + "source": "APIOps Cycles", + "license": "CC-BY-SA 4.0", + "authors": [ + "Osaango Ltd" + ], + "website": "www.apiopscycles.com" + }, + "sections": [ { - "id": "monitoring", + "id": "ownership", "gridPosition": { "column": 0, - "row": 2, + "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 9, - "highlight": false + "fillOrder": 1, + "highlight": true }, { - "id": "support", + "id": "environmentsAndAccess", "gridPosition": { "column": 1, - "row": 2, + "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 10, - "highlight": false + "fillOrder": 2 }, { - "id": "retryReplay", + "id": "testEvidence", "gridPosition": { "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11, - "highlight": false - }, - { - "id": "reconciliation", - "gridPosition": { - "column": 3, - "row": 2, + "row": 0, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 12, - "highlight": false + "fillOrder": 3 }, { - "id": "fallbackRollback", + "id": "monitoringAndSupport", "gridPosition": { "column": 0, - "row": 3, + "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 13, - "highlight": false + "fillOrder": 4 }, { - "id": "incidentOwnership", + "id": "failureAndRecovery", "gridPosition": { "column": 1, - "row": 3, + "row": 1, "colSpan": 1, "rowSpan": 1 }, - "fillOrder": 14, - "highlight": false + "fillOrder": 5 }, { - "id": "testEvidenceKnownRisks", + "id": "documentationRisksAndReadiness", "gridPosition": { "column": 2, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 15, - "highlight": false - }, - { - "id": "readinessStatus", - "gridPosition": { - "column": 3, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 16, - "highlight": true - }, - { - "id": "documentationDependenciesChangeReadiness", - "gridPosition": { - "column": 0, - "row": 4, - "colSpan": 4, - "rowSpan": 1 - }, - "fillOrder": 17, - "highlight": true - } - ] - }, - "integrationSolutionDesignCanvas": { - "id": "integrationSolutionDesignCanvas", - "layout": { - "columns": 4, - "rows": 3 - }, - "metadata": { - "source": "APIOps Cycles", - "license": "CC-BY-SA 4.0", - "authors": [ - "Osaango Ltd" - ], - "website": "www.apiopscycles.com" - }, - "sections": [ - { - "id": "selectedIntegrationStyle", - "gridPosition": { - "column": 0, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 1, - "highlight": true - }, - { - "id": "producerAndConsumer", - "gridPosition": { - "column": 1, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 2 - }, - { - "id": "contractAndSchema", - "gridPosition": { - "column": 2, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 3, - "highlight": true - }, - { - "id": "mappingsAndTransformations", - "gridPosition": { - "column": 3, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4, - "highlight": true - }, - { - "id": "interactionDeliveryPattern", - "gridPosition": { - "column": 0, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 5 - }, - { - "id": "identityAndSecurity", - "gridPosition": { - "column": 1, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 6 - }, - { - "id": "errorRetryReplay", - "gridPosition": { - "column": 2, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 7 - }, - { - "id": "correlationMetadata", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8 - }, - { - "id": "reconciliationRules", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 9 - }, - { - "id": "observability", - "gridPosition": { - "column": 1, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 10 - }, - { - "id": "versioningEvolution", - "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11 - }, - { - "id": "canonicalConsumerSpecificModel", - "gridPosition": { - "column": 3, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 12 - } - ] - }, - "capabilityHypothesisCanvas": { - "id": "capabilityHypothesisCanvas", - "layout": { - "columns": 4, - "rows": 3 - }, - "metadata": { - "source": "APIOps Cycles", - "license": "CC-BY-SA 4.0", - "authors": [ - "Osaango Ltd" - ], - "website": "www.apiopscycles.com" - }, - "sections": [ - { - "id": "hypothesis", - "gridPosition": { - "column": 0, - "row": 0, - "colSpan": 2, - "rowSpan": 1 - }, - "fillOrder": 1, - "highlight": true - }, - { - "id": "targetConsumersUseCases", - "gridPosition": { - "column": 2, - "row": 0, - "colSpan": 2, - "rowSpan": 1 - }, - "fillOrder": 2 - }, - { - "id": "reusableScope", - "gridPosition": { - "column": 0, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 3 - }, - { - "id": "supportingEvidence", - "gridPosition": { - "column": 1, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4 - }, - { - "id": "expectedOutcomes", - "gridPosition": { - "column": 2, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 5 - }, - { - "id": "criticalAssumptions", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 6, - "highlight": true - }, - { - "id": "minimumValidation", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 2, - "rowSpan": 1 - }, - "fillOrder": 7, - "highlight": true - }, - { - "id": "decision", - "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 2, - "rowSpan": 1 - }, - "fillOrder": 8, - "highlight": true - } - ] - }, - "capabilityConsumerProducerRequirementsCanvas": { - "id": "capabilityConsumerProducerRequirementsCanvas", - "layout": { - "columns": 4, - "rows": 3 - }, - "metadata": { - "source": "APIOps Cycles", - "license": "CC-BY-SA 4.0", - "authors": [ - "Osaango Ltd" - ], - "website": "www.apiopscycles.com" - }, - "sections": [ - { - "id": "intendedConsumersContexts", - "gridPosition": { - "column": 0, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 1, - "highlight": true - }, - { - "id": "capabilityOwnerProducerResponsibilities", - "gridPosition": { - "column": 1, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 2, - "highlight": true - }, - { - "id": "discoveryEvaluation", - "gridPosition": { - "column": 2, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 3, - "highlight": false - }, - { - "id": "accessOnboarding", - "gridPosition": { - "column": 3, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4, - "highlight": false - }, - { - "id": "serviceExpectations", - "gridPosition": { - "column": 0, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 5, - "highlight": false - }, - { - "id": "qualityAvailability", - "gridPosition": { - "column": 1, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 6, - "highlight": false - }, - { - "id": "changeLifecycle", - "gridPosition": { - "column": 2, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 7, - "highlight": false - }, - { - "id": "supportIncidentCommunication", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8, - "highlight": false - }, - { - "id": "operationalGovernanceConstraints", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 9, - "highlight": false - }, - { - "id": "producerCommitments", - "gridPosition": { - "column": 1, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 10, - "highlight": false - }, - { - "id": "consumerResponsibilities", - "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11, - "highlight": false - }, - { - "id": "architectureImplications", - "gridPosition": { - "column": 3, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 12, - "highlight": true - } - ] - }, - "capabilityArchitectureDecisionCanvas": { - "id": "capabilityArchitectureDecisionCanvas", - "layout": { - "columns": 4, - "rows": 4 - }, - "metadata": { - "source": "APIOps Cycles", - "license": "CC-BY-SA 4.0", - "authors": [ - "Osaango Ltd" - ], - "website": "www.apiopscycles.com" - }, - "sections": [ - { - "id": "api", - "gridPosition": { - "column": 0, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 1 - }, - { - "id": "event", - "gridPosition": { - "column": 1, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 2 - }, - { - "id": "fileBatch", - "gridPosition": { - "column": 2, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 3 - }, - { - "id": "stream", - "gridPosition": { - "column": 3, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4 - }, - { - "id": "dataProduct", - "gridPosition": { - "column": 0, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 5 - }, - { - "id": "workflow", - "gridPosition": { - "column": 1, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 6 - }, - { - "id": "sharedService", - "gridPosition": { - "column": 2, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 7 - }, - { - "id": "userFacingApplication", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8 - }, - { - "id": "directIntegration", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 9 - }, - { - "id": "platformNativeFeature", - "gridPosition": { - "column": 1, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 10 - }, - { - "id": "humanAssistedService", - "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11 - }, - { - "id": "hybridApproach", - "gridPosition": { - "column": 3, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 12 - }, - { - "id": "evaluationCriteria", - "gridPosition": { - "column": 0, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 13, - "highlight": true - }, - { - "id": "selectedStylePlatform", - "gridPosition": { - "column": 1, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 14, - "highlight": true - }, - { - "id": "rationaleRejectedAlternatives", - "gridPosition": { - "column": 2, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 15, - "highlight": true - }, - { - "id": "assumptionsRisks", - "gridPosition": { - "column": 3, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 16, - "highlight": true - } - ] - }, - "capabilitySolutionDesignCanvas": { - "id": "capabilitySolutionDesignCanvas", - "layout": { - "columns": 4, - "rows": 3 - }, - "metadata": { - "source": "APIOps Cycles", - "license": "CC-BY-SA 4.0", - "authors": [ - "Osaango Ltd" - ], - "website": "www.apiopscycles.com" - }, - "sections": [ - { - "id": "selectedImplementationStyle", - "gridPosition": { - "column": 0, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 1, - "highlight": true - }, - { - "id": "serviceBoundary", - "gridPosition": { - "column": 1, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 2, - "highlight": true - }, - { - "id": "consumerInteractionModel", - "gridPosition": { - "column": 2, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 3, - "highlight": false - }, - { - "id": "dataBusinessConcepts", - "gridPosition": { - "column": 3, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4, - "highlight": false - }, - { - "id": "contractOrServiceDefinition", - "gridPosition": { - "column": 0, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 5, - "highlight": true - }, - { - "id": "responsibilitiesRules", - "gridPosition": { - "column": 1, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 6, - "highlight": false - }, - { - "id": "inputsOutputs", - "gridPosition": { - "column": 2, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 7, - "highlight": false - }, - { - "id": "errorsExceptions", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8, - "highlight": false - }, - { - "id": "lifecycleVersioning", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 9, - "highlight": false - }, - { - "id": "securityPrivacy", - "gridPosition": { - "column": 1, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 10, - "highlight": false - }, - { - "id": "observability", - "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11, - "highlight": false - }, - { - "id": "supportModel", - "gridPosition": { - "column": 3, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 12, - "highlight": false - } - ] - }, - "capabilityReadinessOperationsCanvas": { - "id": "capabilityReadinessOperationsCanvas", - "layout": { - "columns": 4, - "rows": 5 - }, - "metadata": { - "source": "APIOps Cycles", - "license": "CC-BY-SA 4.0", - "authors": [ - "Osaango Ltd" - ], - "website": "www.apiopscycles.com" - }, - "sections": [ - { - "id": "businessOwner", - "gridPosition": { - "column": 0, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 1, - "highlight": true - }, - { - "id": "capabilityOwner", - "gridPosition": { - "column": 1, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 2, - "highlight": true - }, - { - "id": "producerOwner", - "gridPosition": { - "column": 2, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 3, - "highlight": false - }, - { - "id": "operationalOwner", - "gridPosition": { - "column": 3, - "row": 0, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 4, - "highlight": false - }, - { - "id": "consumers", - "gridPosition": { - "column": 0, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 5, - "highlight": false - }, - { - "id": "implementationStyle", - "gridPosition": { - "column": 1, - "row": 1, + "row": 1, "colSpan": 1, "rowSpan": 1 }, "fillOrder": 6, - "highlight": false - }, - { - "id": "environments", - "gridPosition": { - "column": 2, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 7, - "highlight": false - }, - { - "id": "permissionsCredentials", - "gridPosition": { - "column": 3, - "row": 1, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 8, - "highlight": false - }, - { - "id": "testEvidence", - "gridPosition": { - "column": 0, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 9, - "highlight": false - }, - { - "id": "serviceExpectations", - "gridPosition": { - "column": 1, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 10, - "highlight": false - }, - { - "id": "monitoring", - "gridPosition": { - "column": 2, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 11, - "highlight": false - }, - { - "id": "support", - "gridPosition": { - "column": 3, - "row": 2, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 12, - "highlight": false - }, - { - "id": "fallbackContinuity", - "gridPosition": { - "column": 0, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 13, - "highlight": false - }, - { - "id": "changeOwnership", - "gridPosition": { - "column": 1, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 14, - "highlight": false - }, - { - "id": "documentationRunbooks", - "gridPosition": { - "column": 2, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 15, - "highlight": false - }, - { - "id": "readinessStatus", - "gridPosition": { - "column": 3, - "row": 3, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 16, "highlight": true - }, - { - "id": "knownRisks", - "gridPosition": { - "column": 0, - "row": 4, - "colSpan": 2, - "rowSpan": 1 - }, - "fillOrder": 17, - "highlight": false - }, - { - "id": "improvementBacklog", - "gridPosition": { - "column": 1, - "row": 4, - "colSpan": 1, - "rowSpan": 1 - }, - "fillOrder": 18, - "highlight": false } ] } diff --git a/src/data/canvas/localizedData.json b/src/data/canvas/localizedData.json index 066a043..44c0c83 100644 --- a/src/data/canvas/localizedData.json +++ b/src/data/canvas/localizedData.json @@ -71,30 +71,6 @@ "purpose": "Welcher Wert, welches Risiko sowie welche betrieblichen, finanziellen, kunden-, mitarbeiter-, compliance- und strategischen Auswirkungen werden erwartet oder stehen auf dem Spiel?", "howToUse": "Nutzen Sie dies, um erwartete Vorteile und Konsequenzen mit Architektur, Priorisierung, Bereitschaft und Proceed-or-Stop-Entscheidungen zu verbinden. Berücksichtigen Sie auch die Auswirkungen des Nicht-Handelns sowie kritische Risiken und Gegenmaßnahmen.", "sections": { - "availabilityRisks": { - "section": "Risiken der Verfügbarkeit", - "description": "Was sind die potenziellen Risiken für die API-Verfügbarkeit?" - }, - "securityRisks": { - "section": "Sicherheitsrisiken", - "description": "Welche potenziellen Sicherheitsrisiken sind mit der API assoziiert?" - }, - "dataRisks": { - "section": "Datenrisiken", - "description": "Welche potenziellen Risiken bestehen für die Datenintegrität oder -Vertraulichkeit?" - }, - "mitigateAvailabilityRisks": { - "section": "Reduzierung von Risiken der Verfügbarkeit", - "description": "Wie lassen sich Verfügbarkeitsrisiken reduzieren?" - }, - "mitigateSecurityRisks": { - "section": "Reduktion der Sicherheitsrisiken", - "description": "Wie lassen sich Sicherheitsrisiken reduzieren?" - }, - "mitigateDataRisks": { - "section": "Reduktion der Datenrisiken", - "description": "Wie lassen sich Datenrisiken reduzieren?" - }, "expectedBenefits": { "section": "Expected benefits", "description": "What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?" @@ -162,8 +138,8 @@ }, "customerJourneyCanvas": { "title": "Customer Journey Canvas", - "purpose": "Welche Customer Journey oder Partner Journey erzeugt den Bedarf für eine Capability oder Schnittstelle?", - "howToUse": "Beschreiben Sie eine reale Reise eines Kunden, Partners oder Nutzers - nicht die API-Nutzung selbst. Diese Reise macht Probleme, Ziele und Kontext sichtbar und hilft, spätere Anforderungen an Capability- und Schnittstellendesign zu klären.", + "purpose": "Welche Journey erlebt der am weitesten außen liegende sinnvolle Kunde, und was sollte verbessert werden?", + "howToUse": "Beginnen Sie mit dem am weitesten außen liegenden sinnvollen Kunden. Beschreiben Sie zuerst die reale Journey, bevor Sie nach innen zu Capabilities, internen Prozessen oder Implementierungsentscheidungen gehen.", "sections": { "customerDiscoversNeed": { "section": "Kunde erkennt Bedarf", @@ -196,6 +172,10 @@ "interactionProcessingRules": { "section": "Interaktions- und Verarbeitungsregeln", "description": "Wie lauten die Interaktions- und Verarbeitungsregeln bei jedem Schritt?" + }, + "improvementOpportunities": { + "section": "Verbesserungsmöglichkeiten", + "description": "Welche Journey-Schritte zeigen, dass eine zugrunde liegende Capability oder ein Prozess geschaffen, verbessert, automatisiert oder entfernt werden sollte?" } } }, @@ -531,887 +511,424 @@ } }, "automationOpportunityCanvas": { - "title": "Automation Hypothesis Canvas", - "purpose": "Verknüpft Nachweise aus optionalen unterstützenden Canvases mit einer testbaren Automatisierungshypothese, bevor Architektur oder Lieferung festgelegt werden.", - "howToUse": "Beginnen Sie mit dem Automatisierungshypothesen-Canvas. Verweisen Sie nur dort auf Journey, Wertversprechen, Domäne, Business Impact, Kapazität oder andere Nachweise, wo sie relevant sind; wiederholen Sie diese Canvases hier nicht.", + "title": "Automation Hypothesis & Validation Canvas", + "purpose": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "howToUse": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", "sections": { "hypothesis": { - "section": "Hypothesis", - "description": "What do we believe automating which work for which actor will achieve? Use the form: We believe automating [work] for [actor] will achieve [outcome]." - }, - "supportingEvidence": { - "section": "Supporting evidence", - "description": "Which Journey, Value Proposition, Business Impact, Capacity, Domain, or other evidence supports this hypothesis? Link or reference existing artifacts instead of repeating them." + "section": "Automation hypothesis", + "description": "What work do we believe should be automated, and what outcome should it achieve?" }, - "automationScope": { - "section": "Scope of automation", - "description": "Which part of the work is being considered for automation now, and what is explicitly outside scope?" - }, - "responsibilityAndSolutionHypothesis": { - "section": "Anfängliche Implementierungshypothese", - "description": "Welche aktuelle Annahme besteht darüber, wie die Automatisierung umgesetzt werden könnte? Dies ist eine zu validierende Annahme, keine Architekturentscheidung." + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the hypothesis?" }, "criticalAssumptions": { "section": "Critical assumptions", - "description": "Which assumptions could invalidate value, feasibility, safety, operability, compliance, or adoption?" + "description": "What could make the hypothesis wrong, unsafe, or unworkable?" }, "validationExperiment": { "section": "Validation experiment", - "description": "What is the smallest useful PoC or investigation, what evidence and thresholds decide success, and what stop conditions apply?" + "description": "What is the smallest useful test, evidence threshold, and stop condition?" }, "decision": { "section": "Decision", - "description": "What is the evidence-based decision: supported, revise and retest, redesign the process first, or reject?" - } - } - }, - "humanAutomationResponsibilityCanvas": { - "title": "Human-Automation Responsibility Canvas", - "purpose": "Decide what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "howToUse": "List target process steps and decide the most appropriate performer for each step. Capture required oversight, escalation, and evidence so the solution does not assume every step should be automated.", - "sections": { - "processStep": { - "section": "Process step", - "description": "Which step in the target process is being assigned or reviewed?" - }, - "humanResponsibility": { - "section": "Human responsibility", - "description": "What should a person do, decide, approve, review, correct, or own?" - }, - "ruleOrWorkflowResponsibility": { - "section": "Rule or workflow responsibility", - "description": "What can be handled by deterministic rules, orchestration, routing, reminders, or scheduled workflow?" - }, - "agentOrAiResponsibility": { - "section": "Agent or AI responsibility", - "description": "What judgement, language, classification, generation, planning, or assistance may an agent or AI perform?" - }, - "apiOrSystemResponsibility": { - "section": "API or system responsibility", - "description": "What should be performed through system capability, API, event, connector, file, or direct integration?" - }, - "rpaOrUiAutomationResponsibility": { - "section": "RPA or UI automation responsibility", - "description": "Where is UI automation justified because no suitable system, API, event, connector, or data access path exists?" - }, - "requiredOversight": { - "section": "Required oversight", - "description": "What human supervision, approval, confirmation, monitoring, or review is required before or after the step?" - }, - "escalation": { - "section": "Escalation", - "description": "When should the step stop, ask for help, route to a person, or move to another support path?" - }, - "evidenceOrAuditTrail": { - "section": "Evidence or audit trail", - "description": "What record proves what happened, who or what acted, what data was used, and what decision was made?" + "description": "Proceed, revise, redesign the process, or stop?" } } }, "automationWorkflowCanvas": { "title": "Automation Workflow Canvas", - "purpose": "Entwerfen Sie Sequenz, Zustände, Daten, Auslöser, Entscheidungen, Interaktionen, Fehlerpfade und Wiederherstellung des End-to-End-Automatisierungsworkflows.", - "howToUse": "Nutzen Sie die Verantwortungszuordnung aus dem Mensch-Automatisierung-Verantwortungs-Canvas als Eingabe. Fokussieren Sie hier darauf, wie der Workflow läuft, Zustände ändert, Daten austauscht, Ausnahmen behandelt, Nachweise erzeugt und wiederhergestellt wird.", + "purpose": "Entwerfen Sie den internen Workflow, der benötigt wird, um die ausgewählten Kunden- und Capability-Ergebnisse zu liefern.", + "howToUse": "Nutzen Sie Customer Journey, Wertversprechen, Domäne und Validierungsnachweise wieder. Definieren Sie die interne Arbeit, verteilen Sie sie zwischen Menschen und Automatisierung und ergänzen Sie nur Ausführungsdetails.", "sections": { - "trigger": { - "section": "Trigger", - "description": "What event, schedule, user action, message, data change, or manual request starts the automation?" - }, - "inputs": { - "section": "Inputs", - "description": "What data, documents, messages, forms, records, or context are required at the start and during the workflow?" - }, - "workflowStages": { - "section": "Workflow stages and states", - "description": "What are the main workflow stages and states from trigger to completion, including waiting, review, exception, and completion states?" - }, - "decisionsAndRules": { - "section": "Decisions and rules", - "description": "Which deterministic rules, validations, thresholds, policies, or decision points shape the flow?" + "selectedCustomerCapabilityOutcomes": { + "section": "Ausgewählte Kunden- und Capability-Ergebnisse", + "description": "Welche vereinbarten Kunden- und Capability-Ergebnisse muss dieser Workflow liefern?" }, - "agentActions": { - "section": "Automation actions", - "description": "What may the automation, workflow, rule, agent, integration, API, RPA, or system component do at each relevant stage?" + "internalWorkflowSteps": { + "section": "Interne Workflow-Schritte", + "description": "Welche interne Arbeit muss stattfinden, um diese Ergebnisse zu erzeugen?" }, - "systemInteractions": { - "section": "System interactions", - "description": "Which systems, APIs, events, connectors, custom components, files, or screens are called or updated?" + "workAllocationHumanControl": { + "section": "Arbeitsverteilung und menschliche Kontrolle", + "description": "Was bleibt menschlich, was wird automatisiert und wo sind Aufsicht oder Eskalation erforderlich?" }, - "dataSources": { - "section": "Data sources", - "description": "Which source systems, datasets, records, documents, or knowledge sources are used and trusted?" + "inputsOutputsInteractions": { + "section": "Inputs, Outputs und Interaktionen", + "description": "Welche Informationen, Systeme und Übergaben werden benötigt?" }, - "humanTasks": { - "section": "Human checkpoints", - "description": "Where does the responsibility allocation require approval, confirmation, judgement, correction, review, or manual completion?" + "decisionsExceptionsRecovery": { + "section": "Entscheidungen, Ausnahmen und Wiederherstellung", + "description": "Was verändert den Ablauf, was kann fehlschlagen und wie wird die Arbeit wiederhergestellt?" }, - "handoffs": { - "section": "Handoffs and queues", - "description": "Where does work move between automation components, people, support teams, systems, queues, or exception paths?" - }, - "exceptions": { - "section": "Exceptions", - "description": "What error, missing-data, conflicting-data, timeout, permission, unsafe-action, or business exception scenarios must be handled?" - }, - "retriesAndTimeouts": { - "section": "Retries and timeouts", - "description": "Where are retries, timeout limits, duplicate prevention, idempotency, pause rules, or compensation required?" - }, - "outputs": { - "section": "Outputs", - "description": "What records, decisions, messages, documents, updates, notifications, or outcomes are produced?" - }, - "auditEvidence": { - "section": "Audit evidence", - "description": "What log, trace, approval, run history, input snapshot, output record, or explanation proves correct operation?" - }, - "monitoringPoints": { - "section": "Monitoring points", - "description": "Which run, failure, exception, latency, cost, intervention, quality, safety, or outcome metrics should be observed?" - }, - "recoveryPath": { - "section": "Recovery path", - "description": "How can the process be paused, rolled back, compensated, rerun, corrected, or completed manually?" + "evidenceMonitoring": { + "section": "Nachweise und Monitoring", + "description": "Was belegt den korrekten Betrieb und zeigt, ob das beabsichtigte Ergebnis erreicht wurde?" } } }, "automationArchitectureDecisionCanvas": { "title": "Automation Architecture Decision Canvas", - "purpose": "Vergleichen und begründen Sie alternative Implementierungsmechanismen für eine Automatisierungslösung.", - "howToUse": "Markieren Sie jeden Kandidatenmechanismus als betrachtet, ausgewählt, abgelehnt oder nicht relevant. Vergleichen Sie nur tragfähige Kandidaten einzeln und als Hybrid und begründen Sie dann den empfohlenen Implementierungsansatz anhand von Machbarkeit, Zuverlässigkeit, Sicherheit, Wartbarkeit, Latenz, Skalierbarkeit, Kosten, Abhängigkeiten, Testbarkeit, Beobachtbarkeit, Wiederherstellbarkeit, Kompetenzen und Architektur-Fit.", + "purpose": "Choose the implementation approach using evidence already gathered.", + "howToUse": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", "sections": { - "nativeFeature": { - "section": "Native Funktion", - "description": "Kann eine vorhandene Systemfunktion diesen Schritt mit akzeptabler Zuverlässigkeit, Kontrollen und Verantwortung lösen?" - }, - "workflow": { - "section": "Workflow", - "description": "Wo passen Workflow-Orchestrierung, Planung, Routing, Genehmigung, Benachrichtigung oder Koordination am besten?" - }, - "rule": { - "section": "Regel", - "description": "Welche Entscheidungen können als deterministische Geschäftsregeln, Richtlinienprüfungen, Validierungen oder Berechnungen umgesetzt werden?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which requirements, capacity, location, impact, and responsibility decisions constrain the choice?" }, - "agent": { - "section": "Agent", - "description": "Wo könnte ein Agent oder KI sicher Urteilsvermögen, Sprachverständnis, Generierung, Planung oder Unterstützung einbringen?" + "viableOptions": { + "section": "Viable options", + "description": "Which human, workflow, rule, agent, API, connector, custom, or UI automation options remain viable?" }, - "connector": { - "section": "Connector", - "description": "Welche Low-Code-, Plattform-, SaaS-, Datei-, Nachrichten- oder Daten-Connectors sind geeignet?" - }, - "api": { - "section": "API", - "description": "Wo ist ein API-Aufruf die beste Wahl für zuverlässige, gesteuerte und testbare Systeminteraktion?" - }, - "event": { - "section": "Event", - "description": "Wo sollte die Lösung auf Events reagieren, Events veröffentlichen oder konsumieren?" - }, - "customCode": { - "section": "Individueller Code", - "description": "Wo ist individueller Code gerechtfertigt, weil Standardfähigkeiten unzureichend oder zu riskant sind?" - }, - "rpa": { - "section": "RPA", - "description": "Wo ist Desktop- oder UI-Automatisierung gerechtfertigt, und welche Kontrollen für Fragilität und Wiederherstellung sind erforderlich?" - }, - "humanTask": { - "section": "Menschliche Aufgabe", - "description": "Welche Schritte sollten wegen Urteilsvermögen, Verantwortlichkeit, Risiko, Einwilligung, Richtlinien oder Ausnahmebehandlung menschlich bleiben?" - }, - "feasibilityReliabilitySecurity": { - "section": "Feasibility, reliability, security", - "description": "How do candidates compare on technical feasibility, expected reliability, identity, authorization, data exposure, and control strength?" - }, - "maintainabilityScalabilityCost": { - "section": "Maintainability, scalability, cost", - "description": "How do candidates compare on change effort, operating cost, licence cost, transaction volume, peak load, and lifecycle maintenance?" - }, - "latencyObservabilityRecoverability": { - "section": "Latency, observability, recoverability", - "description": "How do candidates compare on timing needs, monitoring, logs, traceability, retry, compensation, and manual recovery?" - }, - "skillsVendorFit": { - "section": "Skills, vendor dependency, architectural fit", - "description": "What skills, ownership, platform dependencies, governance constraints, and architecture standards affect the decision?" - }, - "recommendedHybridApproach": { - "section": "Recommended hybrid approach", - "description": "Which combination of people, rules, workflows, agents, systems, APIs, events, custom code, and UI automation should be used?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style or hybrid is selected?" }, "decisionRationale": { "section": "Decision rationale", - "description": "Why is this approach preferred over the alternatives, and what evidence supports the decision?" + "description": "Why does the selected approach fit best?" }, - "openQuestionsAndRisks": { - "section": "Open questions and risks", - "description": "Which assumptions, risks, dependencies, or unresolved constraints must be validated before delivery or release?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" + }, + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "automationReadinessOperationsCanvas": { "title": "Automation Readiness & Operations Canvas", - "purpose": "Bereiten Sie das Betriebsmodell für eine sicher freigegebene, unterstützte, überwachte und wiederherstellbare Automatisierung vor.", - "howToUse": "Nutzen Sie dies während der Lieferung, um Verantwortung, Umgebungen, Zugriff, Nachweise, Monitoring, Support, Fallback, Rollback, Runbooks, bekannte Risiken und den Freigabebereitschaftsstatus vorzubereiten. Verwenden Sie später die Bereitschaftscheckliste für das formale Gate.", + "purpose": "Prepare the minimum operating evidence needed before readiness review.", + "howToUse": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Who accepts business value, process impact, residual risk, and release timing?" - }, - "operationalOwner": { - "section": "Operational owner", - "description": "Who owns runtime supervision, incidents, support, runbooks, changes, and recovery?" + "ownership": { + "section": "Ownership", + "description": "Who owns business outcomes, operations, support, and changes?" }, - "users": { - "section": "Users", - "description": "Which users, operators, approvers, support teams, or process participants are affected?" - }, - "permissions": { - "section": "Permissions", - "description": "What human, service, system, data, role, and approval permissions are required and approved?" - }, - "credentials": { - "section": "Credentials", - "description": "How are credentials, secrets, certificates, tokens, delegated access, and service identities managed?" - }, - "environments": { - "section": "Environments", - "description": "Which development, test, staging, production, desktop, cloud, or platform environments are used?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, permissions, credentials, and identities ready?" }, "testEvidence": { "section": "Test evidence", - "description": "What proves functional correctness, rule behavior, integration behavior, agent behavior, permissions, performance, and exceptions?" - }, - "exceptionHandling": { - "section": "Exception handling", - "description": "How are errors, missing data, unsafe actions, failed runs, retries, timeouts, and handoffs handled?" + "description": "What proves correct, safe, and reliable behavior?" }, - "monitoring": { - "section": "Monitoring", - "description": "Which run, failure, exception, latency, cost, intervention, value, safety, and outcome signals are monitored?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, incidents, users, and operators be supported?" }, - "support": { - "section": "Support", - "description": "Who supports users and operators, how are incidents raised, and what service expectations apply?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will exceptions, fallback, rollback, and manual recovery work?" }, - "manualFallback": { - "section": "Manual fallback", - "description": "How can work continue manually if the automation is paused, unavailable, incorrect, or unsafe?" - }, - "rollback": { - "section": "Rollback", - "description": "How can changes, actions, data updates, releases, or workflow versions be reversed or compensated?" - }, - "documentation": { - "section": "Documentation", - "description": "What operating instructions, design records, architecture decisions, user guidance, and runbooks are ready?" - }, - "deploymentDecision": { - "section": "Freigabebereitschaftsstatus", - "description": "Was ist vor der formalen Bereitschaftsentscheidung noch unvollständig, bedingt oder blockierend?" - }, - "knownRisks": { - "section": "Known risks", - "description": "Which risks are accepted, mitigated, deferred, or blocking release?" - }, - "improvementBacklog": { - "section": "Improvement backlog", - "description": "Which improvements, unresolved assumptions, PoC findings, and future enhancements should be prioritized next?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are documentation, risks, conditions, and blocking gaps clear?" } } }, "integrationCapabilityHypothesisCanvas": { - "title": "Integration Capability Hypothesis Canvas", - "purpose": "Priorisieren Sie eine wiederverwendbare Integrationsfähigkeit, indem Sie Verbraucher-, Wert-, Domänen-, Ownership-, Wiederverwendungs- und Viabilitätsnachweise mit klarem Umfang, Annahmen, Validierungsschritt und Fortfahren-oder-Stoppen-Entscheidung verbinden.", - "howToUse": "Beginnen Sie hier vor der Architekturentscheidung. Verweisen Sie nur dort auf Journey, Wertversprechen, Domäne, Geschäftsmodell, Impact, Kapazität oder andere Nachweise, wo sie die Hypothese stützen.", + "title": "Integration Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable integration capability should proceed.", + "howToUse": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", "sections": { - "hypothesis": { - "section": "Integrationsfähigkeitshypothese", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Integrationsfähigkeitshypothese festgehalten werden?" - }, - "consumersAndReuseScope": { - "section": "Vorgesehene Consumer und Wiederverwendungsumfang", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Vorgesehene Consumer und Wiederverwendungsumfang festgehalten werden?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed integration capability and reuse scope are being tested?" }, - "providerAndOwner": { - "section": "Provider und Owner", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Provider und Owner festgehalten werden?" - }, - "supportingEvidence": { - "section": "Unterstützende Nachweise", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Unterstützende Nachweise festgehalten werden?" - }, - "implementationStyleHypothesis": { - "section": "Anfängliche Implementierungsstil-Hypothese", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Anfängliche Implementierungsstil-Hypothese festgehalten werden?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { - "section": "Kritische Annahmen", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Kritische Annahmen festgehalten werden?" + "section": "Critical assumptions", + "description": "What could invalidate value, reuse, ownership, feasibility, or adoption?" }, - "validationExperiment": { - "section": "Validierungsexperiment", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Validierungsexperiment festgehalten werden?" + "validationStep": { + "section": "Validation step", + "description": "What is the smallest useful validation and success threshold?" }, "decision": { - "section": "Entscheidung", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Entscheidung festgehalten werden?" + "section": "Decision", + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "integrationConsumerProviderRequirementsCanvas": { - "title": "Integration Consumer & Provider Requirements Canvas", - "purpose": "Erfassen Sie, was konsumierende Systeme, Teams, Produzenten, Provider und Betreiber benötigen, bevor die Integrationsumsetzung ausgewählt oder entworfen wird.", - "howToUse": "Nutzen Sie dies, um Onboarding, Zugriff, Umgebungen, Identität, Kompatibilität, Serviceerwartungen, Datenqualität, Support und Wiederherstellungsanforderungen explizit zu machen.", + "title": "Integration Consumer & Provider Commitments Canvas", + "purpose": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "howToUse": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", "sections": { - "consumerSystemsAndTeams": { - "section": "Consumer-Systeme und Teams", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Consumer-Systeme und Teams festgehalten werden?" - }, - "providerResponsibilities": { - "section": "Provider-Verantwortlichkeiten", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Provider-Verantwortlichkeiten festgehalten werden?" - }, - "interactionAndDataNeeds": { - "section": "Interaktions- und Datenbedarfe", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Interaktions- und Datenbedarfe festgehalten werden?" - }, - "onboardingAndAccess": { - "section": "Onboarding und Zugriff", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Onboarding und Zugriff festgehalten werden?" - }, - "environmentsAndTestAccess": { - "section": "Umgebungen und Testzugriff", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Umgebungen und Testzugriff festgehalten werden?" + "selectedPartiesAndUseCases": { + "section": "Selected parties and use cases", + "description": "Which producers, providers, consumers, and use cases are covered?" }, - "credentialsAndIdentity": { - "section": "Credentials und Identität", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Credentials und Identität festgehalten werden?" + "providerCommitments": { + "section": "Provider commitments", + "description": "What will providers deliver, maintain, monitor, and support?" }, - "compatibilityAndVersioning": { - "section": "Kompatibilität und Versionierung", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Kompatibilität und Versionierung festgehalten werden?" + "consumerCommitments": { + "section": "Consumer commitments", + "description": "What must consumers test, protect, operate, and communicate?" }, - "serviceExpectations": { - "section": "Serviceerwartungen", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Serviceerwartungen festgehalten werden?" + "accessAndValidationAgreement": { + "section": "Access and validation", + "description": "How will access, environments, credentials, and conformance be handled?" }, - "dataQualityAndObservability": { - "section": "Datenqualität und Beobachtbarkeit", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Datenqualität und Beobachtbarkeit festgehalten werden?" + "failureAndRecoveryAgreement": { + "section": "Failure and recovery", + "description": "Who handles failures, replay, duplicates, reconciliation, and recovery?" }, - "supportAndFailureHandling": { - "section": "Support und Fehlerbehandlung", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Support und Fehlerbehandlung festgehalten werden?" - }, - "replayReconciliationRecovery": { - "section": "Replay, Abstimmung, Wiederherstellung", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Replay, Abstimmung, Wiederherstellung festgehalten werden?" + "changeAndLifecycleAgreement": { + "section": "Change and lifecycle", + "description": "How will compatibility, migration, notice, deprecation, and retirement work?" } } }, "integrationArchitectureDecisionCanvas": { "title": "Integration Architecture Decision Canvas", - "purpose": "Vergleichen und begründen Sie Integrationsstile, Plattformfähigkeiten, Governance-Randbedingungen und abgelehnte Alternativen.", - "howToUse": "Nutzen Sie die gemeinsame Kandidatenstatus-Auswahl, um jeden Kandidatenstil als betrachtet, ausgewählt, abgelehnt oder nicht relevant zu markieren. Vergleichen Sie tragfähige Optionen nach Timing, Kopplung, Dateneigentum, Konsistenz, Zuverlässigkeit, Sicherheit, Wartbarkeit, Beobachtbarkeit, Wiederherstellung, Kosten, Governance und Skills.", + "purpose": "Choose the integration style and platform using evidence already gathered.", + "howToUse": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", "sections": { - "synchronousApi": { - "section": "Synchrone API", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Synchrone API festgehalten werden?" - }, - "eventDriven": { - "section": "Asynchrones Event", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Asynchrones Event festgehalten werden?" - }, - "messagingQueue": { - "section": "Messaging oder Queue", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Messaging oder Queue festgehalten werden?" - }, - "batchFileExchange": { - "section": "Batch- oder Dateiaustausch", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Batch- oder Dateiaustausch festgehalten werden?" - }, - "stream": { - "section": "Stream", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Stream festgehalten werden?" - }, - "etlElt": { - "section": "ETL oder ELT", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für ETL oder ELT festgehalten werden?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which commitments, capacity, location, impact, and domain decisions constrain the choice?" }, - "dataProduct": { - "section": "Datenprodukt", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Datenprodukt festgehalten werden?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, messaging, file, stream, data, connector, platform, or custom options remain viable?" }, - "directDatabase": { - "section": "Direkte Datenbankintegration", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Direkte Datenbankintegration festgehalten werden?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which integration style, platform, or hybrid is selected?" }, - "sharedPlatform": { - "section": "Gemeinsame Integrationsplattform", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Gemeinsame Integrationsplattform festgehalten werden?" - }, - "pointToPoint": { - "section": "Point-to-Point", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Point-to-Point festgehalten werden?" - }, - "managedConnector": { - "section": "Managed Connector", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Managed Connector festgehalten werden?" - }, - "customIntegration": { - "section": "Custom Integration", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Custom Integration festgehalten werden?" - }, - "hybridApproach": { - "section": "Hybrider Ansatz", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Hybrider Ansatz festgehalten werden?" - }, - "evaluationCriteria": { - "section": "Bewertungskriterien", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Bewertungskriterien festgehalten werden?" - }, - "selectedStyleAndPlatform": { - "section": "Ausgewählter Stil und Plattform", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Ausgewählter Stil und Plattform festgehalten werden?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "rationaleAndRejectedAlternatives": { - "section": "Begründung und abgelehnte Alternativen", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Begründung und abgelehnte Alternativen festgehalten werden?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "openRisksAndAssumptions": { - "section": "Offene Risiken und Annahmen", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Offene Risiken und Annahmen festgehalten werden?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "integrationReadinessOperationsCanvas": { "title": "Integration Readiness & Operations Canvas", - "purpose": "Bereiten Sie das Betriebsmodell für eine sicher freigegebene, unterstützte, überwachte, wiederherstellbare und wiederverwendbare Integrationsfähigkeit vor.", - "howToUse": "Nutzen Sie dies während der Lieferung, um Ownership, Umgebungen, Credentials, Deployment, Monitoring, Support, Retry, Replay, Abstimmung, Fallback, Rollback, Incidents, Testnachweise, Risiken und Readiness-Status vorzubereiten.", + "purpose": "Prepare the minimum operating evidence needed before integration readiness review.", + "howToUse": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business Owner", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Business Owner festgehalten werden?" + "ownership": { + "section": "Ownership", + "description": "Who owns business, integration, producer, consumer, platform, and incident responsibilities?" }, - "integrationOwner": { - "section": "Integration Owner", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Integration Owner festgehalten werden?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, credentials, connectivity, permissions, and sequencing ready?" }, - "producerOwners": { - "section": "Producer Owner", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Producer Owner festgehalten werden?" - }, - "consumerOwners": { - "section": "Consumer Owner", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Consumer Owner festgehalten werden?" - }, - "platformOwner": { - "section": "Platform Owner", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Platform Owner festgehalten werden?" - }, - "environments": { - "section": "Umgebungen", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Umgebungen festgehalten werden?" - }, - "credentials": { - "section": "Credentials", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Credentials festgehalten werden?" - }, - "deployment": { - "section": "Deployment", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Deployment festgehalten werden?" - }, - "monitoring": { - "section": "Monitoring", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Monitoring festgehalten werden?" - }, - "support": { - "section": "Support", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Support festgehalten werden?" - }, - "retryReplay": { - "section": "Retry und Replay", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Retry und Replay festgehalten werden?" - }, - "reconciliation": { - "section": "Abstimmung", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Abstimmung festgehalten werden?" - }, - "fallbackRollback": { - "section": "Fallback und Rollback", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Fallback und Rollback festgehalten werden?" - }, - "incidentOwnership": { - "section": "Incident Ownership", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Incident Ownership festgehalten werden?" + "testEvidence": { + "section": "Test evidence", + "description": "What proves contract, mapping, compatibility, quality, resilience, and recovery?" }, - "testEvidenceKnownRisks": { - "section": "Testnachweise und bekannte Risiken", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Testnachweise und bekannte Risiken festgehalten werden?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will producers, consumers, platforms, incidents, and service questions be supported?" }, - "readinessStatus": { - "section": "Readiness-Status", - "description": "Welche Angaben, Nachweise, Entscheidungen und offenen Punkte müssen für Readiness-Status festgehalten werden?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will retry, replay, duplicates, reconciliation, fallback, and compensation work?" }, - "documentationDependenciesChangeReadiness": { - "section": "Dokumentation, Abhängigkeiten und Änderungsbereitschaft", - "description": "Sind Verträge, Mappings, Runbooks, Abhängigkeiten, Migrationsanweisungen, Deployment-Sequenzierung, Cutover, Rückwärtskompatibilität, Version Ownership und Änderungsverantwortungen bereit?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are contracts, runbooks, dependencies, risks, conditions, and blocking gaps clear?" } } }, "integrationSolutionDesignCanvas": { "title": "Integration Solution Design Canvas", - "purpose": "Fasst das vollständige Integrationsdesign über Implementierungsstile hinweg zusammen, einschließlich Verträgen, Schemas, Datenstrukturen, Mappings, Lieferverhalten, Security, Fehlern, Beobachtbarkeit, Abstimmung und Versionierung.", - "howToUse": "Nutzen Sie dies als primäres Solution-Design-Artefakt nach der Architekturentscheidung. Nutzen Sie Interaction Canvas, REST-, Event-, GraphQL-, Datei-, Stream-, Datenprodukt- oder Messaging-Ressourcen nur als bedingte Detailunterstützung.", + "purpose": "Refine the selected architecture into an implementable integration design.", + "howToUse": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", "sections": { - "selectedIntegrationStyle": { - "section": "Ausgewählter Integrationsstil", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Ausgewählter Integrationsstil festgehalten werden?" - }, - "producerAndConsumer": { - "section": "Producer und Consumer", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Producer und Consumer festgehalten werden?" - }, - "contractAndSchema": { - "section": "Vertrag und Schema", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Vertrag und Schema festgehalten werden?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which architecture, domain, interaction, and commitment decisions are reused?" }, - "mappingsAndTransformations": { - "section": "Mappings und Transformationen", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Mappings und Transformationen festgehalten werden?" + "contractAndModel": { + "section": "Contract and model", + "description": "What contract, schema, data model, and version define the integration?" }, - "interactionDeliveryPattern": { - "section": "Interaktions- oder Liefermuster", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Interaktions- oder Liefermuster festgehalten werden?" + "mappingAndDelivery": { + "section": "Mapping and delivery", + "description": "What transformations, delivery pattern, and metadata are required?" }, - "identityAndSecurity": { - "section": "Identität und Security", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Identität und Security festgehalten werden?" + "errorsAndRecovery": { + "section": "Errors and recovery", + "description": "How are failures, retries, replay, duplicates, and reconciliation handled?" }, - "errorRetryReplay": { - "section": "Fehlermodell, Retry, Replay", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Fehlermodell, Retry, Replay festgehalten werden?" + "securityAndTrust": { + "section": "Security and trust", + "description": "What identity, access, privacy, and trust controls apply?" }, - "correlationMetadata": { - "section": "Korrelation und Metadaten", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Korrelation und Metadaten festgehalten werden?" - }, - "reconciliationRules": { - "section": "Abstimmungsregeln", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Abstimmungsregeln festgehalten werden?" - }, - "observability": { - "section": "Beobachtbarkeit", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Beobachtbarkeit festgehalten werden?" - }, - "versioningEvolution": { - "section": "Versionierung und Weiterentwicklung", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Versionierung und Weiterentwicklung festgehalten werden?" - }, - "canonicalConsumerSpecificModel": { - "section": "Kanonisches vs. consumer-spezifisches Modell", - "description": "Welche Designentscheidungen, Regeln, Nachweise und offenen Punkte müssen für Kanonisches vs. consumer-spezifisches Modell festgehalten werden?" + "observabilityAndEvolution": { + "section": "Observability and evolution", + "description": "How will the integration be monitored, changed, migrated, and deprecated?" } } }, "capabilityHypothesisCanvas": { - "title": "Capability Hypothesis Canvas", - "purpose": "Priorisieren Sie eine wiederverwendbare digitale Fähigkeitshypothese, indem Sie Consumer-, Wert-, Domänen-, Ownership-, Viabilitäts- und Wiederverwendungsnachweise mit klarem Umfang, Annahmen, Validierungsschritt und Entscheidung verbinden.", - "howToUse": "Welche Entscheidungen, Nachweise und offenen Punkte müssen für Capability Hypothesis Canvas festgehalten werden?", + "title": "Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable digital capability should proceed.", + "howToUse": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", "sections": { - "hypothesis": { - "section": "Fähigkeitshypothese", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Fähigkeitshypothese festgehalten werden?" - }, - "targetConsumersUseCases": { - "section": "Ziel-Consumer und Anwendungsfälle", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Ziel-Consumer und Anwendungsfälle festgehalten werden?" - }, - "reusableScope": { - "section": "Vorgesehener Wiederverwendungsumfang", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Vorgesehener Wiederverwendungsumfang festgehalten werden?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed capability and reusable scope are being tested?" }, - "supportingEvidence": { - "section": "Unterstützende Nachweise", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Unterstützende Nachweise festgehalten werden?" - }, - "expectedOutcomes": { - "section": "Erwartete Ergebnisse", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Erwartete Ergebnisse festgehalten werden?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { - "section": "Kritische Annahmen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Kritische Annahmen festgehalten werden?" + "section": "Critical assumptions", + "description": "What could invalidate value, reuse, ownership, sustainability, or adoption?" }, "minimumValidation": { - "section": "Minimale Validierung", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Minimale Validierung festgehalten werden?" + "section": "Minimum validation", + "description": "What is the smallest useful validation and success threshold?" }, "decision": { - "section": "Entscheidung", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Entscheidung festgehalten werden?" + "section": "Decision", + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "capabilityConsumerProducerRequirementsCanvas": { - "title": "Consumer & Producer Requirements Canvas", - "purpose": "Erfassen Sie, was Consumer, Producer, Owner, Betreiber und Support-Teams von einer wiederverwendbaren Fähigkeit benötigen, bevor Implementierungsstil oder Design festgelegt werden.", - "howToUse": "Welche Entscheidungen, Nachweise und offenen Punkte müssen für Consumer & Producer Requirements Canvas festgehalten werden?", + "title": "Capability Consumer & Producer Commitments Canvas", + "purpose": "Agree mutual commitments for providing and consuming a reusable capability.", + "howToUse": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", "sections": { - "intendedConsumersContexts": { - "section": "Vorgesehene Consumer und Kontexte", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Vorgesehene Consumer und Kontexte festgehalten werden?" - }, - "capabilityOwnerProducerResponsibilities": { - "section": "Capability Owner und Producer-Verantwortlichkeiten", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Capability Owner und Producer-Verantwortlichkeiten festgehalten werden?" - }, - "discoveryEvaluation": { - "section": "Auffindbarkeit und Bewertung", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Auffindbarkeit und Bewertung festgehalten werden?" - }, - "accessOnboarding": { - "section": "Zugriff und Onboarding", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Zugriff und Onboarding festgehalten werden?" - }, - "serviceExpectations": { - "section": "Serviceerwartungen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Serviceerwartungen festgehalten werden?" + "selectedConsumersAndUseCases": { + "section": "Selected consumers and use cases", + "description": "Which consumers and usage contexts are covered?" }, - "qualityAvailability": { - "section": "Qualitäts- und Verfügbarkeitserwartungen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Qualitäts- und Verfügbarkeitserwartungen festgehalten werden?" + "ownerAndProducerCommitments": { + "section": "Owner and producer commitments", + "description": "What will owners and producers provide, maintain, monitor, and support?" }, - "changeLifecycle": { - "section": "Änderungs- und Lifecycle-Erwartungen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Änderungs- und Lifecycle-Erwartungen festgehalten werden?" - }, - "supportIncidentCommunication": { - "section": "Support und Incident-Kommunikation", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Support und Incident-Kommunikation festgehalten werden?" - }, - "operationalGovernanceConstraints": { - "section": "Operative und Governance-Randbedingungen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Operative und Governance-Randbedingungen festgehalten werden?" + "consumerResponsibilities": { + "section": "Consumer responsibilities", + "description": "What must consumers do for appropriate use, access, testing, and feedback?" }, - "producerCommitments": { - "section": "Producer-Verpflichtungen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Producer-Verpflichtungen festgehalten werden?" + "accessAndOnboardingAgreement": { + "section": "Access and onboarding", + "description": "What discovery, approval, testing, and onboarding path is agreed?" }, - "consumerResponsibilities": { - "section": "Consumer-Verantwortlichkeiten", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Consumer-Verantwortlichkeiten festgehalten werden?" + "serviceAndLifecycleAgreement": { + "section": "Service and lifecycle", + "description": "What service, change, deprecation, and retirement commitments are agreed?" }, - "architectureImplications": { - "section": "Architekturimplikationen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Architekturimplikationen festgehalten werden?" + "openCommitments": { + "section": "Open commitments", + "description": "What remains unresolved before architecture or delivery?" } } }, "capabilityArchitectureDecisionCanvas": { "title": "Capability Architecture Decision Canvas", - "purpose": "Vergleichen Sie Implementierungsoptionen und dokumentieren Sie ausgewählten Implementierungsstil, Plattform, Begründung, abgelehnte Alternativen, Annahmen und Risiken der Fähigkeit.", - "howToUse": "Nutzen Sie die gemeinsame Kandidatenstatus-Auswahl, um jeden Kandidatenstil als betrachtet, ausgewählt, abgelehnt oder nicht relevant zu markieren. Vergleichen Sie tragfähige Optionen nach Consumer-Bedarfen, Wiederverwendung, Kopplung, Latenz, Timing, Volumen, Dateneigentum, Konsistenz, Security, Trust- und Location-Grenzen, Zuverlässigkeit, Operabilität, Kosten, Skills, Plattform-Fit, Governance, Auffindbarkeit und Lifecycle Management.", + "purpose": "Choose how the capability will be delivered using evidence already gathered.", + "howToUse": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", "sections": { - "api": { - "section": "API", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für API festgehalten werden?" - }, - "event": { - "section": "Event", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Event festgehalten werden?" - }, - "fileBatch": { - "section": "Datei oder Batch", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Datei oder Batch festgehalten werden?" - }, - "stream": { - "section": "Stream", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Stream festgehalten werden?" - }, - "dataProduct": { - "section": "Datenprodukt", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Datenprodukt festgehalten werden?" - }, - "workflow": { - "section": "Workflow", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Workflow festgehalten werden?" - }, - "sharedService": { - "section": "Shared Service", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Shared Service festgehalten werden?" - }, - "userFacingApplication": { - "section": "User-facing Application", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für User-facing Application festgehalten werden?" - }, - "directIntegration": { - "section": "Direkte Integration", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Direkte Integration festgehalten werden?" - }, - "platformNativeFeature": { - "section": "Plattformnative Funktion", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Plattformnative Funktion festgehalten werden?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which earlier decisions and constraints shape the implementation choice?" }, - "humanAssistedService": { - "section": "Menschlich unterstützter Service", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Menschlich unterstützter Service festgehalten werden?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, workflow, application, data product, shared service, human service, or hybrid options remain viable?" }, - "hybridApproach": { - "section": "Hybrider Ansatz", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Hybrider Ansatz festgehalten werden?" - }, - "evaluationCriteria": { - "section": "Bewertungskriterien", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Bewertungskriterien festgehalten werden?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style and enabling platform are selected?" }, - "selectedStylePlatform": { - "section": "Ausgewählter Stil und Plattform", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Ausgewählter Stil und Plattform festgehalten werden?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "rationaleRejectedAlternatives": { - "section": "Begründung und abgelehnte Alternativen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Begründung und abgelehnte Alternativen festgehalten werden?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "assumptionsRisks": { - "section": "Annahmen und Risiken", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Annahmen und Risiken festgehalten werden?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "capabilitySolutionDesignCanvas": { "title": "Capability Solution Design Canvas", - "purpose": "Entwerfen Sie, wie Consumer über den ausgewählten Implementierungsstil auf die Fähigkeit zugreifen, mit ihr interagieren, sie erhalten oder nutzen.", - "howToUse": "Welche Entscheidungen, Nachweise und offenen Punkte müssen für Capability Solution Design Canvas festgehalten werden?", + "purpose": "Refine the selected implementation style into a clear consumer-facing capability design.", + "howToUse": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", "sections": { - "selectedImplementationStyle": { - "section": "Ausgewählter Implementierungsstil", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Ausgewählter Implementierungsstil festgehalten werden?" - }, - "serviceBoundary": { - "section": "Servicegrenze", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Servicegrenze festgehalten werden?" - }, - "consumerInteractionModel": { - "section": "Consumer-Interaktionsmodell", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Consumer-Interaktionsmodell festgehalten werden?" - }, - "dataBusinessConcepts": { - "section": "Daten- und Business-Konzepte", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Daten- und Business-Konzepte festgehalten werden?" - }, - "contractOrServiceDefinition": { - "section": "Vertrag oder Service Definition", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Vertrag oder Service Definition festgehalten werden?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which earlier journey, value, domain, commitment, and architecture decisions are reused?" }, - "responsibilitiesRules": { - "section": "Verantwortlichkeiten und Regeln", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Verantwortlichkeiten und Regeln festgehalten werden?" + "boundaryAndInteraction": { + "section": "Boundary and interaction", + "description": "What belongs inside the capability, and how do consumers use it?" }, - "inputsOutputs": { - "section": "Inputs und Outputs", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Inputs und Outputs festgehalten werden?" - }, - "errorsExceptions": { - "section": "Fehler und Ausnahmen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Fehler und Ausnahmen festgehalten werden?" + "contractRulesAndOutcomes": { + "section": "Contract, rules, and outcomes", + "description": "What behavior, responsibilities, inputs, outputs, and outcomes are promised?" }, - "lifecycleVersioning": { - "section": "Lifecycle und Versionierung", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Lifecycle und Versionierung festgehalten werden?" + "errorsAndSecurity": { + "section": "Errors and security", + "description": "How are exceptions, access, privacy, and trust handled?" }, - "securityPrivacy": { - "section": "Security und Datenschutz", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Security und Datenschutz festgehalten werden?" + "lifecycleAndSupport": { + "section": "Lifecycle and support", + "description": "How will change, versioning, support, deprecation, and retirement work?" }, "observability": { - "section": "Beobachtbarkeit", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Beobachtbarkeit festgehalten werden?" - }, - "supportModel": { - "section": "Supportmodell", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Supportmodell festgehalten werden?" + "section": "Observability", + "description": "What health, usage, quality, value, and consumer signals must be visible?" } } }, "capabilityReadinessOperationsCanvas": { "title": "Capability Readiness & Operations Canvas", - "purpose": "Bereiten Sie das Betriebsmodell für eine wiederverwendbare Fähigkeit vor der formalen Readiness-Entscheidung vor.", - "howToUse": "Welche Entscheidungen, Nachweise und offenen Punkte müssen für Capability Readiness & Operations Canvas festgehalten werden?", + "purpose": "Prepare the minimum operating evidence needed before capability readiness review.", + "howToUse": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", "sections": { - "businessOwner": { - "section": "Business Owner", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Business Owner festgehalten werden?" - }, - "capabilityOwner": { - "section": "Capability Owner", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Capability Owner festgehalten werden?" - }, - "producerOwner": { - "section": "Producer Owner", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Producer Owner festgehalten werden?" - }, - "operationalOwner": { - "section": "Operational Owner", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Operational Owner festgehalten werden?" - }, - "consumers": { - "section": "Consumer", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Consumer festgehalten werden?" + "ownership": { + "section": "Ownership", + "description": "Who owns value, the capability lifecycle, production, operations, support, and changes?" }, - "implementationStyle": { - "section": "Implementierungsstil", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Implementierungsstil festgehalten werden?" - }, - "environments": { - "section": "Umgebungen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Umgebungen festgehalten werden?" - }, - "permissionsCredentials": { - "section": "Berechtigungen und Credentials", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Berechtigungen und Credentials festgehalten werden?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are required environments, access, permissions, and credentials ready?" }, "testEvidence": { - "section": "Testnachweise", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Testnachweise festgehalten werden?" - }, - "serviceExpectations": { - "section": "Serviceerwartungen", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Serviceerwartungen festgehalten werden?" - }, - "monitoring": { - "section": "Monitoring", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Monitoring festgehalten werden?" - }, - "support": { - "section": "Support", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Support festgehalten werden?" - }, - "fallbackContinuity": { - "section": "Fallback und Kontinuität", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Fallback und Kontinuität festgehalten werden?" - }, - "changeOwnership": { - "section": "Change Ownership", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Change Ownership festgehalten werden?" - }, - "documentationRunbooks": { - "section": "Dokumentation und Runbooks", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Dokumentation und Runbooks festgehalten werden?" + "section": "Test evidence", + "description": "What proves outcomes, quality, security, compatibility, resilience, and consumer usability?" }, - "readinessStatus": { - "section": "Readiness-Status", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Readiness-Status festgehalten werden?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, usage, value, incidents, consumers, and operators be supported?" }, - "knownRisks": { - "section": "Bekannte Risiken", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Bekannte Risiken festgehalten werden?" + "failureAndRecovery": { + "section": "Continuity and recovery", + "description": "How will service continue, degrade safely, recover, or fall back?" }, - "improvementBacklog": { - "section": "Verbesserungs-Backlog", - "description": "Welche konkreten Entscheidungen, Nachweise, Verantwortlichkeiten, Risiken und nächsten Schritte müssen für Verbesserungs-Backlog festgehalten werden?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are service definitions, runbooks, risks, conditions, and blocking gaps clear?" } } } @@ -1488,30 +1005,6 @@ "purpose": "What value, risk, operational, financial, customer, employee, compliance, and strategic impact is expected or at stake?", "howToUse": "Use this to connect expected benefits and consequences to architecture, prioritization, readiness, and proceed-or-stop decisions. Include the impact of not proceeding as well as critical risks and mitigations.", "sections": { - "availabilityRisks": { - "section": "Availability Risks", - "description": "What are the potential risks to capability availability?" - }, - "securityRisks": { - "section": "Security Risks", - "description": "What are the potential security risks associated with the capability?" - }, - "dataRisks": { - "section": "Data Risks", - "description": "What are the potential risks to data integrity or confidentiality?" - }, - "mitigateAvailabilityRisks": { - "section": "Mitigate Availability Risks", - "description": "How can the capability owner mitigate the availability risks?" - }, - "mitigateSecurityRisks": { - "section": "Mitigate Security Risks", - "description": "How can the capability owner mitigate the security risks?" - }, - "mitigateDataRisks": { - "section": "Mitigate Data Risks", - "description": "How can the capability owner mitigate the data risks?" - }, "expectedBenefits": { "section": "Expected benefits", "description": "What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?" @@ -1579,8 +1072,8 @@ }, "customerJourneyCanvas": { "title": "Customer Journey Canvas", - "purpose": "What customer, partner, or consumer journey is the capability intended to support?", - "howToUse": "Describe the real-life customer, partner, or consumer journey, not the solution usage itself, to reveal pain points, goals, context, inputs, outputs, and experience expectations.", + "purpose": "What journey does the most external meaningful customer experience, and what should improve?", + "howToUse": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", "sections": { "customerDiscoversNeed": { "section": "Customer Discovers Need", @@ -1613,6 +1106,10 @@ "interactionProcessingRules": { "section": "Interaction & Processing Rules", "description": "What are the interaction and processing rules at each step?" + }, + "improvementOpportunities": { + "section": "Improvement opportunities", + "description": "Which journey steps indicate that an underlying capability or process should be created, improved, automated, or removed?" } } }, @@ -1948,887 +1445,424 @@ } }, "automationOpportunityCanvas": { - "title": "Automation Hypothesis Canvas", - "purpose": "Link evidence from optional supporting canvases to a testable automation hypothesis before committing to architecture or delivery.", - "howToUse": "Start with the Automation Hypothesis Canvas. Reference Journey, Value Proposition, Domain, Business Impact, Capacity, or other evidence only where it is relevant; do not repeat those canvases here.", + "title": "Automation Hypothesis & Validation Canvas", + "purpose": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "howToUse": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", "sections": { "hypothesis": { - "section": "Hypothesis", - "description": "What do we believe automating which work for which actor will achieve? Use the form: We believe automating [work] for [actor] will achieve [outcome]." - }, - "supportingEvidence": { - "section": "Supporting evidence", - "description": "Which Journey, Value Proposition, Business Impact, Capacity, Domain, or other evidence supports this hypothesis? Link or reference existing artifacts instead of repeating them." + "section": "Automation hypothesis", + "description": "What work do we believe should be automated, and what outcome should it achieve?" }, - "automationScope": { - "section": "Scope of automation", - "description": "Which part of the work is being considered for automation now, and what is explicitly outside scope?" - }, - "responsibilityAndSolutionHypothesis": { - "section": "Initial implementation hypothesis", - "description": "What is the current assumption about how the automation might be implemented? This is an assumption to validate, not an architecture decision." + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the hypothesis?" }, "criticalAssumptions": { "section": "Critical assumptions", - "description": "Which assumptions could invalidate value, feasibility, safety, operability, compliance, or adoption?" + "description": "What could make the hypothesis wrong, unsafe, or unworkable?" }, "validationExperiment": { "section": "Validation experiment", - "description": "What is the smallest useful PoC or investigation, what evidence and thresholds decide success, and what stop conditions apply?" + "description": "What is the smallest useful test, evidence threshold, and stop condition?" }, "decision": { "section": "Decision", - "description": "What is the evidence-based decision: supported, revise and retest, redesign the process first, or reject?" - } - } - }, - "humanAutomationResponsibilityCanvas": { - "title": "Human-Automation Responsibility Canvas", - "purpose": "Decide what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "howToUse": "List target process steps and decide the most appropriate performer for each step. Capture required oversight, escalation, and evidence so the solution does not assume every step should be automated.", - "sections": { - "processStep": { - "section": "Process step", - "description": "Which step in the target process is being assigned or reviewed?" - }, - "humanResponsibility": { - "section": "Human responsibility", - "description": "What should a person do, decide, approve, review, correct, or own?" - }, - "ruleOrWorkflowResponsibility": { - "section": "Rule or workflow responsibility", - "description": "What can be handled by deterministic rules, orchestration, routing, reminders, or scheduled workflow?" - }, - "agentOrAiResponsibility": { - "section": "Agent or AI responsibility", - "description": "What judgement, language, classification, generation, planning, or assistance may an agent or AI perform?" - }, - "apiOrSystemResponsibility": { - "section": "API or system responsibility", - "description": "What should be performed through system capability, API, event, connector, file, or direct integration?" - }, - "rpaOrUiAutomationResponsibility": { - "section": "RPA or UI automation responsibility", - "description": "Where is UI automation justified because no suitable system, API, event, connector, or data access path exists?" - }, - "requiredOversight": { - "section": "Required oversight", - "description": "What human supervision, approval, confirmation, monitoring, or review is required before or after the step?" - }, - "escalation": { - "section": "Escalation", - "description": "When should the step stop, ask for help, route to a person, or move to another support path?" - }, - "evidenceOrAuditTrail": { - "section": "Evidence or audit trail", - "description": "What record proves what happened, who or what acted, what data was used, and what decision was made?" + "description": "Proceed, revise, redesign the process, or stop?" } } }, "automationWorkflowCanvas": { "title": "Automation Workflow Canvas", - "purpose": "Design the sequence, states, data, triggers, decisions, interactions, failure paths, and recovery for the end-to-end automation workflow.", - "howToUse": "Use the responsibility allocation from the Human-Automation Responsibility Canvas as an input. Focus here on how the workflow runs, changes state, exchanges data, handles exceptions, produces evidence, and recovers.", + "purpose": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", + "howToUse": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", "sections": { - "trigger": { - "section": "Trigger", - "description": "What event, schedule, user action, message, data change, or manual request starts the automation?" - }, - "inputs": { - "section": "Inputs", - "description": "What data, documents, messages, forms, records, or context are required at the start and during the workflow?" + "selectedCustomerCapabilityOutcomes": { + "section": "Selected customer and capability outcomes", + "description": "Which agreed customer outcomes and capability results must this workflow deliver?" }, - "workflowStages": { - "section": "Workflow stages and states", - "description": "What are the main workflow stages and states from trigger to completion, including waiting, review, exception, and completion states?" + "internalWorkflowSteps": { + "section": "Internal workflow steps", + "description": "What internal work must happen to produce those outcomes?" }, - "decisionsAndRules": { - "section": "Decisions and rules", - "description": "Which deterministic rules, validations, thresholds, policies, or decision points shape the flow?" + "workAllocationHumanControl": { + "section": "Work allocation and human control", + "description": "What remains human, what is automated, and where are oversight or escalation required?" }, - "agentActions": { - "section": "Automation actions", - "description": "What may the automation, workflow, rule, agent, integration, API, RPA, or system component do at each relevant stage?" + "inputsOutputsInteractions": { + "section": "Inputs, outputs, and interactions", + "description": "What information, systems, and handoffs are needed?" }, - "systemInteractions": { - "section": "System interactions", - "description": "Which systems, APIs, events, connectors, custom components, files, or screens are called or updated?" + "decisionsExceptionsRecovery": { + "section": "Decisions, exceptions, and recovery", + "description": "What changes the flow, what can fail, and how is work recovered?" }, - "dataSources": { - "section": "Data sources", - "description": "Which source systems, datasets, records, documents, or knowledge sources are used and trusted?" - }, - "humanTasks": { - "section": "Human checkpoints", - "description": "Where does the responsibility allocation require approval, confirmation, judgement, correction, review, or manual completion?" - }, - "handoffs": { - "section": "Handoffs and queues", - "description": "Where does work move between automation components, people, support teams, systems, queues, or exception paths?" - }, - "exceptions": { - "section": "Exceptions", - "description": "What error, missing-data, conflicting-data, timeout, permission, unsafe-action, or business exception scenarios must be handled?" - }, - "retriesAndTimeouts": { - "section": "Retries and timeouts", - "description": "Where are retries, timeout limits, duplicate prevention, idempotency, pause rules, or compensation required?" - }, - "outputs": { - "section": "Outputs", - "description": "What records, decisions, messages, documents, updates, notifications, or outcomes are produced?" - }, - "auditEvidence": { - "section": "Audit evidence", - "description": "What log, trace, approval, run history, input snapshot, output record, or explanation proves correct operation?" - }, - "monitoringPoints": { - "section": "Monitoring points", - "description": "Which run, failure, exception, latency, cost, intervention, quality, safety, or outcome metrics should be observed?" - }, - "recoveryPath": { - "section": "Recovery path", - "description": "How can the process be paused, rolled back, compensated, rerun, corrected, or completed manually?" + "evidenceMonitoring": { + "section": "Evidence and monitoring", + "description": "What proves correct operation and shows whether the intended outcome was achieved?" } } }, "automationArchitectureDecisionCanvas": { "title": "Automation Architecture Decision Canvas", - "purpose": "Compare and justify alternative implementation mechanisms for an automation solution.", - "howToUse": "Mark each candidate mechanism as considered, selected, rejected, or not relevant. Compare only the viable candidates individually and as a hybrid, then justify the recommended implementation approach using feasibility, reliability, security, maintainability, latency, scalability, cost, dependency, testability, observability, recoverability, skills, and architectural fit.", + "purpose": "Choose the implementation approach using evidence already gathered.", + "howToUse": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", "sections": { - "nativeFeature": { - "section": "Native feature", - "description": "Can an existing system capability solve this step with acceptable reliability, controls, and ownership?" - }, - "workflow": { - "section": "Workflow", - "description": "Where is workflow orchestration, scheduling, routing, approval, notification, or coordination the best fit?" - }, - "rule": { - "section": "Rule", - "description": "Which decisions can be implemented as deterministic business rules, policy checks, validations, or calculations?" - }, - "agent": { - "section": "Agent", - "description": "Where could an agent or AI safely add judgement, language understanding, generation, planning, or assistance?" - }, - "connector": { - "section": "Connector", - "description": "Which low-code, platform, SaaS, file, message, or data connectors are viable?" - }, - "api": { - "section": "API", - "description": "Where is an API call the best fit for reliable, governed, testable system interaction?" - }, - "event": { - "section": "Event", - "description": "Where should the solution react to, publish, or consume events?" - }, - "customCode": { - "section": "Custom code", - "description": "Where is custom code justified because standard capabilities are insufficient or too risky?" - }, - "rpa": { - "section": "RPA", - "description": "Where is desktop or UI automation justified, and what fragility or recovery controls are required?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which requirements, capacity, location, impact, and responsibility decisions constrain the choice?" }, - "humanTask": { - "section": "Human task", - "description": "Which steps should remain human because of judgement, accountability, risk, consent, policy, or exception handling?" + "viableOptions": { + "section": "Viable options", + "description": "Which human, workflow, rule, agent, API, connector, custom, or UI automation options remain viable?" }, - "feasibilityReliabilitySecurity": { - "section": "Feasibility, reliability, security", - "description": "How do candidates compare on technical feasibility, expected reliability, identity, authorization, data exposure, and control strength?" - }, - "maintainabilityScalabilityCost": { - "section": "Maintainability, scalability, cost", - "description": "How do candidates compare on change effort, operating cost, licence cost, transaction volume, peak load, and lifecycle maintenance?" - }, - "latencyObservabilityRecoverability": { - "section": "Latency, observability, recoverability", - "description": "How do candidates compare on timing needs, monitoring, logs, traceability, retry, compensation, and manual recovery?" - }, - "skillsVendorFit": { - "section": "Skills, vendor dependency, architectural fit", - "description": "What skills, ownership, platform dependencies, governance constraints, and architecture standards affect the decision?" - }, - "recommendedHybridApproach": { - "section": "Recommended hybrid approach", - "description": "Which combination of people, rules, workflows, agents, systems, APIs, events, custom code, and UI automation should be used?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style or hybrid is selected?" }, "decisionRationale": { "section": "Decision rationale", - "description": "Why is this approach preferred over the alternatives, and what evidence supports the decision?" + "description": "Why does the selected approach fit best?" }, - "openQuestionsAndRisks": { - "section": "Open questions and risks", - "description": "Which assumptions, risks, dependencies, or unresolved constraints must be validated before delivery or release?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" + }, + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "automationReadinessOperationsCanvas": { "title": "Automation Readiness & Operations Canvas", - "purpose": "Prepare the operating model for a safely released, supported, monitored, and recoverable automation.", - "howToUse": "Use this during delivery to prepare ownership, environments, access, evidence, monitoring, support, fallback, rollback, runbooks, known risks, and the deployment decision. Use the readiness checklist later for the release gate.", + "purpose": "Prepare the minimum operating evidence needed before readiness review.", + "howToUse": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Who accepts business value, process impact, residual risk, and release timing?" - }, - "operationalOwner": { - "section": "Operational owner", - "description": "Who owns runtime supervision, incidents, support, runbooks, changes, and recovery?" - }, - "users": { - "section": "Users", - "description": "Which users, operators, approvers, support teams, or process participants are affected?" - }, - "permissions": { - "section": "Permissions", - "description": "What human, service, system, data, role, and approval permissions are required and approved?" + "ownership": { + "section": "Ownership", + "description": "Who owns business outcomes, operations, support, and changes?" }, - "credentials": { - "section": "Credentials", - "description": "How are credentials, secrets, certificates, tokens, delegated access, and service identities managed?" - }, - "environments": { - "section": "Environments", - "description": "Which development, test, staging, production, desktop, cloud, or platform environments are used?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, permissions, credentials, and identities ready?" }, "testEvidence": { "section": "Test evidence", - "description": "What proves functional correctness, rule behavior, integration behavior, agent behavior, permissions, performance, and exceptions?" - }, - "exceptionHandling": { - "section": "Exception handling", - "description": "How are errors, missing data, unsafe actions, failed runs, retries, timeouts, and handoffs handled?" - }, - "monitoring": { - "section": "Monitoring", - "description": "Which run, failure, exception, latency, cost, intervention, value, safety, and outcome signals are monitored?" - }, - "support": { - "section": "Support", - "description": "Who supports users and operators, how are incidents raised, and what service expectations apply?" + "description": "What proves correct, safe, and reliable behavior?" }, - "manualFallback": { - "section": "Manual fallback", - "description": "How can work continue manually if the automation is paused, unavailable, incorrect, or unsafe?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, incidents, users, and operators be supported?" }, - "rollback": { - "section": "Rollback", - "description": "How can changes, actions, data updates, releases, or workflow versions be reversed or compensated?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will exceptions, fallback, rollback, and manual recovery work?" }, - "documentation": { - "section": "Documentation", - "description": "What operating instructions, design records, architecture decisions, user guidance, and runbooks are ready?" - }, - "deploymentDecision": { - "section": "Release readiness status", - "description": "What remains incomplete, conditional, or blocking before the formal readiness decision?" - }, - "knownRisks": { - "section": "Known risks", - "description": "Which risks are accepted, mitigated, deferred, or blocking release?" - }, - "improvementBacklog": { - "section": "Improvement backlog", - "description": "Which improvements, unresolved assumptions, PoC findings, and future enhancements should be prioritized next?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are documentation, risks, conditions, and blocking gaps clear?" } } }, "integrationCapabilityHypothesisCanvas": { - "title": "Integration Capability Hypothesis Canvas", - "purpose": "Prioritize a reusable integration capability hypothesis by linking consumer, value, domain, ownership, reuse, and viability evidence to a clear scope, assumptions, validation step, and proceed-or-stop decision.", - "howToUse": "Start here before architecture selection. Reference journey, value proposition, domain, business model, impact, capacity, or other evidence only where it supports the hypothesis.", + "title": "Integration Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable integration capability should proceed.", + "howToUse": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", "sections": { - "hypothesis": { - "section": "Integration capability hypothesis", - "description": "What reusable integration capability do we believe should exist, for which consumers, and what outcome should it achieve?" - }, - "consumersAndReuseScope": { - "section": "Intended consumers and reuse scope", - "description": "Which current and future consumers, use cases, boundaries, and reuse limits are in scope?" - }, - "providerAndOwner": { - "section": "Provider and owner", - "description": "Who provides the capability, who owns it as a product, and who operates it?" - }, - "supportingEvidence": { - "section": "Supporting evidence", - "description": "Which journey, value, domain, business model, impact, capacity, or other evidence supports this hypothesis?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed integration capability and reuse scope are being tested?" }, - "implementationStyleHypothesis": { - "section": "Initial implementation-style hypothesis", - "description": "What is the current assumption about API, event, file, stream, data product, direct integration, connector, or hybrid style?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { "section": "Critical assumptions", - "description": "Which assumptions could invalidate value, feasibility, ownership, reuse, operability, compliance, or adoption?" + "description": "What could invalidate value, reuse, ownership, feasibility, or adoption?" }, - "validationExperiment": { - "section": "Validation experiment", - "description": "What is the smallest useful validation step, what evidence decides success, and what stop conditions apply?" + "validationStep": { + "section": "Validation step", + "description": "What is the smallest useful validation and success threshold?" }, "decision": { "section": "Decision", - "description": "What is the evidence-based decision: proceed, revise and retest, narrow scope, or reject?" + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "integrationConsumerProviderRequirementsCanvas": { - "title": "Integration Consumer & Provider Requirements Canvas", - "purpose": "Capture what consumer systems, teams, producers, providers, and operators need before selecting or designing the integration implementation.", - "howToUse": "Use this to make onboarding, access, environments, identity, compatibility, service expectations, data quality, support, and recovery requirements explicit.", + "title": "Integration Consumer & Provider Commitments Canvas", + "purpose": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "howToUse": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", "sections": { - "consumerSystemsAndTeams": { - "section": "Consumer systems and teams", - "description": "Which systems, teams, partners, products, processes, or data consumers need this integration capability?" - }, - "providerResponsibilities": { - "section": "Provider responsibilities", - "description": "What must the producer, provider, platform, or owning team commit to?" - }, - "interactionAndDataNeeds": { - "section": "Interaction and data needs", - "description": "What data, events, commands, files, timing, freshness, ordering, and transformation expectations must be supported?" + "selectedPartiesAndUseCases": { + "section": "Selected parties and use cases", + "description": "Which producers, providers, consumers, and use cases are covered?" }, - "onboardingAndAccess": { - "section": "Onboarding and access", - "description": "How do consumers discover, request access, get approved, and start using the capability?" - }, - "environmentsAndTestAccess": { - "section": "Environments and test access", - "description": "Which sandbox, test, staging, production, partner, or synthetic-data environments are needed?" - }, - "credentialsAndIdentity": { - "section": "Credentials and identity", - "description": "What identities, credentials, secrets, certificates, tokens, permissions, or trust boundaries are required?" - }, - "compatibilityAndVersioning": { - "section": "Compatibility and versioning", - "description": "What compatibility, change notice, migration, deprecation, and versioning expectations apply?" + "providerCommitments": { + "section": "Provider commitments", + "description": "What will providers deliver, maintain, monitor, and support?" }, - "serviceExpectations": { - "section": "Service expectations", - "description": "What availability, latency, throughput, support hours, incident, and service-level expectations matter?" + "consumerCommitments": { + "section": "Consumer commitments", + "description": "What must consumers test, protect, operate, and communicate?" }, - "dataQualityAndObservability": { - "section": "Data quality and observability", - "description": "What validation, completeness, consistency, reconciliation, traceability, status, and monitoring visibility is required?" + "accessAndValidationAgreement": { + "section": "Access and validation", + "description": "How will access, environments, credentials, and conformance be handled?" }, - "supportAndFailureHandling": { - "section": "Support and failure handling", - "description": "How are errors, partial failures, timeouts, consumer issues, provider incidents, and support escalations handled?" + "failureAndRecoveryAgreement": { + "section": "Failure and recovery", + "description": "Who handles failures, replay, duplicates, reconciliation, and recovery?" }, - "replayReconciliationRecovery": { - "section": "Replay, reconciliation, recovery", - "description": "What replay, retry, duplicate handling, ordering, reconciliation, fallback, restart, and recovery expectations apply?" + "changeAndLifecycleAgreement": { + "section": "Change and lifecycle", + "description": "How will compatibility, migration, notice, deprecation, and retirement work?" } } }, "integrationArchitectureDecisionCanvas": { "title": "Integration Architecture Decision Canvas", - "purpose": "Compare and justify integration implementation styles, platform capabilities, governance constraints, and rejected alternatives.", - "howToUse": "Use the shared candidate status control to mark each candidate style as considered, selected, rejected, or not relevant. Compare viable options against timing, coupling, data ownership, consistency, reliability, security, maintainability, observability, recovery, cost, governance, and skills.", + "purpose": "Choose the integration style and platform using evidence already gathered.", + "howToUse": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", "sections": { - "synchronousApi": { - "section": "Synchronous API", - "description": "Where does request-response interaction fit the timing, coupling, reliability, and consumer experience needs?" - }, - "eventDriven": { - "section": "Asynchronous event", - "description": "Where should events be published or consumed to decouple producers and consumers?" - }, - "messagingQueue": { - "section": "Messaging or queue", - "description": "Where are queues, topics, routing, buffering, delivery guarantees, or dead-letter handling needed?" - }, - "batchFileExchange": { - "section": "Batch or file exchange", - "description": "Where do scheduled files, batches, manifests, schema validation, restartability, or delivery windows fit?" - }, - "stream": { - "section": "Stream", - "description": "Where is continuous high-volume, low-latency, ordered, or replayable data movement needed?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which commitments, capacity, location, impact, and domain decisions constrain the choice?" }, - "etlElt": { - "section": "ETL or ELT", - "description": "Where are extraction, transformation, loading, lineage, and data platform operations the right fit?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, messaging, file, stream, data, connector, platform, or custom options remain viable?" }, - "dataProduct": { - "section": "Data product", - "description": "Where should curated, governed, discoverable data be exposed as a reusable product?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which integration style, platform, or hybrid is selected?" }, - "directDatabase": { - "section": "Direct database integration", - "description": "Where is direct database access considered, and what coupling, ownership, security, and change risks does it create?" - }, - "sharedPlatform": { - "section": "Shared integration platform", - "description": "Where should platform capabilities, gateways, brokers, iPaaS, catalogs, or managed services be used?" - }, - "pointToPoint": { - "section": "Point-to-point", - "description": "Where is a narrow point-to-point integration acceptable, and what reuse or maintainability tradeoffs follow?" - }, - "managedConnector": { - "section": "Managed connector", - "description": "Where can SaaS, low-code, marketplace, or vendor-managed connectors satisfy the need?" - }, - "customIntegration": { - "section": "Custom integration", - "description": "Where is custom code justified because standard patterns or connectors are insufficient?" - }, - "hybridApproach": { - "section": "Hybrid approach", - "description": "Which combination of API, event, file, stream, data product, connector, platform, and custom integration is needed?" - }, - "evaluationCriteria": { - "section": "Evaluation criteria", - "description": "How do options compare on interaction, timing, coupling, data ownership, consistency, reliability, replay, latency, volume, security, maintainability, observability, cost, governance, vendor dependency, and skills?" - }, - "selectedStyleAndPlatform": { - "section": "Selected style and platform", - "description": "Which style or hybrid and which platform capabilities are selected?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "rationaleAndRejectedAlternatives": { - "section": "Rationale and rejected alternatives", - "description": "Why is this decision preferred, and why were other viable alternatives rejected?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "openRisksAndAssumptions": { - "section": "Open risks and assumptions", - "description": "Which risks, assumptions, dependencies, standards, or unresolved constraints must be tracked before release?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "integrationReadinessOperationsCanvas": { "title": "Integration Readiness & Operations Canvas", - "purpose": "Prepare the operating model for a safely released, supported, monitored, recoverable, and reusable integration capability.", - "howToUse": "Use this during delivery to prepare ownership, environments, credentials, deployment, monitoring, support, retry, replay, reconciliation, fallback, rollback, incidents, test evidence, risks, and readiness status.", + "purpose": "Prepare the minimum operating evidence needed before integration readiness review.", + "howToUse": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Who owns business value, reuse intent, funding, prioritization, and release acceptance?" - }, - "integrationOwner": { - "section": "Integration owner", - "description": "Who owns the integration capability lifecycle, changes, roadmap, and operational accountability?" - }, - "producerOwners": { - "section": "Producer owners", - "description": "Who owns source systems, events, data, schemas, contracts, and producer-side incidents?" - }, - "consumerOwners": { - "section": "Consumer owners", - "description": "Which consumer owners must be ready for onboarding, testing, migration, and production use?" - }, - "platformOwner": { - "section": "Platform owner", - "description": "Who owns gateway, broker, iPaaS, data platform, runtime, network, or shared platform responsibilities?" - }, - "environments": { - "section": "Environments", - "description": "Which development, test, sandbox, staging, production, partner, and recovery environments are ready?" - }, - "credentials": { - "section": "Credentials", - "description": "How are credentials, certificates, secrets, tokens, service identities, and access approvals managed?" - }, - "deployment": { - "section": "Deployment", - "description": "How are build, release, configuration, migration, cutover, and rollback managed?" + "ownership": { + "section": "Ownership", + "description": "Who owns business, integration, producer, consumer, platform, and incident responsibilities?" }, - "monitoring": { - "section": "Monitoring", - "description": "Which availability, latency, throughput, queue, stream, batch, file, data quality, incident, and consumer signals are monitored?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, credentials, connectivity, permissions, and sequencing ready?" }, - "support": { - "section": "Support", - "description": "Who supports producers, consumers, platform operations, incidents, changes, and service questions?" - }, - "retryReplay": { - "section": "Retry and replay", - "description": "How are retries, replay, dead-letter handling, duplicate handling, ordering, and idempotency handled?" - }, - "reconciliation": { - "section": "Reconciliation", - "description": "How are records, events, files, totals, states, and downstream outcomes reconciled?" - }, - "fallbackRollback": { - "section": "Fallback and rollback", - "description": "How can consumers or operations continue safely during outage, degradation, incorrect data, or release rollback? Distinguish rollback from compensating actions where downstream effects cannot be reversed." + "testEvidence": { + "section": "Test evidence", + "description": "What proves contract, mapping, compatibility, quality, resilience, and recovery?" }, - "incidentOwnership": { - "section": "Incident ownership", - "description": "Who leads incidents across producer, integration, platform, consumer, and business boundaries?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will producers, consumers, platforms, incidents, and service questions be supported?" }, - "testEvidenceKnownRisks": { - "section": "Test evidence and known risks", - "description": "What test evidence, accepted residual risks, conditions, and remediation actions are documented?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will retry, replay, duplicates, reconciliation, fallback, and compensation work?" }, - "readinessStatus": { + "documentationRisksAndReadiness": { "section": "Readiness status", - "description": "What remains incomplete, conditional, or blocking before the formal readiness decision?" - }, - "documentationDependenciesChangeReadiness": { - "section": "Documentation, dependencies, and change readiness", - "description": "Are contracts, mappings, runbooks, dependencies, migration instructions, deployment sequencing, cutover, backward compatibility, version ownership, and change responsibilities ready?" + "description": "Are contracts, runbooks, dependencies, risks, conditions, and blocking gaps clear?" } } }, "integrationSolutionDesignCanvas": { "title": "Integration Solution Design Canvas", - "purpose": "Summarize the complete integration design across implementation styles, including contracts, schemas, data structures, mappings, delivery behavior, security, errors, observability, reconciliation, and versioning.", - "howToUse": "Use this as the primary solution-design artifact after the architecture decision. Use Interaction Canvas, REST, Event, GraphQL, file, stream, data product, or messaging resources as conditional deeper design support.", + "purpose": "Refine the selected architecture into an implementable integration design.", + "howToUse": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", "sections": { - "selectedIntegrationStyle": { - "section": "Selected integration style", - "description": "Which selected style or hybrid from the architecture decision is this design implementing?" - }, - "producerAndConsumer": { - "section": "Producer and consumer", - "description": "Which producer, provider, platform, consumer systems, teams, and ownership boundaries are involved?" - }, - "contractAndSchema": { - "section": "Contract and schema", - "description": "Which interface contract, event schema, message schema, file schema, data contract, or specification defines the integration?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which architecture, domain, interaction, and commitment decisions are reused?" }, - "mappingsAndTransformations": { - "section": "Mappings and transformations", - "description": "What source-to-target mappings, transformation rules, validation rules, and canonical or consumer-specific models are required?" + "contractAndModel": { + "section": "Contract and model", + "description": "What contract, schema, data model, and version define the integration?" }, - "interactionDeliveryPattern": { - "section": "Interaction or delivery pattern", - "description": "What request, event, queue, file, batch, stream, connector, orchestration, webhook, B2B/EDI, or data-product delivery pattern applies?" + "mappingAndDelivery": { + "section": "Mapping and delivery", + "description": "What transformations, delivery pattern, and metadata are required?" }, - "identityAndSecurity": { - "section": "Identity and security", - "description": "What identities, credentials, authorization, encryption, trust boundaries, privacy, and audit controls are required?" + "errorsAndRecovery": { + "section": "Errors and recovery", + "description": "How are failures, retries, replay, duplicates, and reconciliation handled?" }, - "errorRetryReplay": { - "section": "Error model, retry, replay", - "description": "How are errors, partial failures, retries, replay, idempotency, duplicate handling, ordering, and dead letters handled?" + "securityAndTrust": { + "section": "Security and trust", + "description": "What identity, access, privacy, and trust controls apply?" }, - "correlationMetadata": { - "section": "Correlation and metadata", - "description": "What correlation IDs, message metadata, file names, manifests, batch control records, timestamps, and trace fields are required?" - }, - "reconciliationRules": { - "section": "Reconciliation rules", - "description": "How are records, events, files, totals, states, and downstream outcomes reconciled?" - }, - "observability": { - "section": "Observability", - "description": "Which logs, metrics, traces, status, alerts, data-quality signals, and consumer-visible health indicators are needed?" - }, - "versioningEvolution": { - "section": "Versioning and evolution", - "description": "How will compatibility, schema evolution, version ownership, migration, deprecation, and consumer change be managed?" - }, - "canonicalConsumerSpecificModel": { - "section": "Canonical vs consumer-specific model", - "description": "Where should the design use shared canonical models, and where are consumer-specific variations justified?" + "observabilityAndEvolution": { + "section": "Observability and evolution", + "description": "How will the integration be monitored, changed, migrated, and deprecated?" } } }, "capabilityHypothesisCanvas": { - "title": "Capability Hypothesis Canvas", - "purpose": "Prioritize a reusable digital capability hypothesis by linking consumer, value, domain, ownership, viability, and reuse evidence to a clear scope, assumptions, validation step, and decision.", - "howToUse": "Use Capability Hypothesis Canvas as the primary artifact for this station. Use supporting canvases only where the necessary evidence does not already exist.", + "title": "Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable digital capability should proceed.", + "howToUse": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", "sections": { - "hypothesis": { - "section": "Capability hypothesis", - "description": "What reusable digital capability do we believe should exist, for whom, and what outcome should it achieve?" - }, - "targetConsumersUseCases": { - "section": "Target consumers and use cases", - "description": "Which current and potential consumers and use cases are in scope?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed capability and reusable scope are being tested?" }, - "reusableScope": { - "section": "Intended reusable scope", - "description": "What should be reusable across consumers, and what is explicitly outside scope?" - }, - "supportingEvidence": { - "section": "Supporting evidence", - "description": "Which journey, value proposition, domain, impact, capacity, market, or operational evidence supports the hypothesis?" - }, - "expectedOutcomes": { - "section": "Expected outcomes", - "description": "What consumer, business, operational, compliance, or ecosystem outcomes are expected?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { "section": "Critical assumptions", - "description": "Which assumptions could invalidate value, reuse, feasibility, ownership, sustainability, or adoption?" + "description": "What could invalidate value, reuse, ownership, sustainability, or adoption?" }, "minimumValidation": { "section": "Minimum validation", - "description": "What is the smallest useful validation activity, and what evidence and thresholds determine success?" + "description": "What is the smallest useful validation and success threshold?" }, "decision": { "section": "Decision", - "description": "Should the capability proceed, be narrowed, revised and retested, or rejected?" + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "capabilityConsumerProducerRequirementsCanvas": { - "title": "Consumer & Producer Requirements Canvas", - "purpose": "Capture what consumers, producers, owners, operators, and support teams need from a reusable capability before selecting or designing the implementation style.", - "howToUse": "Use Consumer & Producer Requirements Canvas as the primary artifact for this station. Use supporting canvases only where the necessary evidence does not already exist.", + "title": "Capability Consumer & Producer Commitments Canvas", + "purpose": "Agree mutual commitments for providing and consuming a reusable capability.", + "howToUse": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", "sections": { - "intendedConsumersContexts": { - "section": "Intended consumers and contexts", - "description": "Who will use or consume the capability, in which processes, products, systems, or journeys?" + "selectedConsumersAndUseCases": { + "section": "Selected consumers and use cases", + "description": "Which consumers and usage contexts are covered?" }, - "capabilityOwnerProducerResponsibilities": { - "section": "Capability owner and producer responsibilities", - "description": "Who is accountable for the productized capability, and what must producer teams provide and maintain?" + "ownerAndProducerCommitments": { + "section": "Owner and producer commitments", + "description": "What will owners and producers provide, maintain, monitor, and support?" }, - "discoveryEvaluation": { - "section": "Discovery and evaluation", - "description": "How should consumers find, understand, compare, and evaluate the capability?" + "consumerResponsibilities": { + "section": "Consumer responsibilities", + "description": "What must consumers do for appropriate use, access, testing, and feedback?" }, - "accessOnboarding": { + "accessAndOnboardingAgreement": { "section": "Access and onboarding", - "description": "How should consumers request access, test, onboard, and begin using it?" - }, - "serviceExpectations": { - "section": "Service expectations", - "description": "What availability, timeliness, quality, support, and service commitments are expected?" - }, - "qualityAvailability": { - "section": "Quality and availability expectations", - "description": "What accuracy, completeness, consistency, freshness, reliability, and continuity requirements apply?" - }, - "changeLifecycle": { - "section": "Change and lifecycle expectations", - "description": "What notice, compatibility, migration, versioning, deprecation, and retirement expectations apply?" - }, - "supportIncidentCommunication": { - "section": "Support and incident communication", - "description": "How are issues raised, owned, communicated, escalated, and resolved?" + "description": "What discovery, approval, testing, and onboarding path is agreed?" }, - "operationalGovernanceConstraints": { - "section": "Operational and governance constraints", - "description": "What security, privacy, compliance, funding, policy, platform, or operating constraints apply?" + "serviceAndLifecycleAgreement": { + "section": "Service and lifecycle", + "description": "What service, change, deprecation, and retirement commitments are agreed?" }, - "producerCommitments": { - "section": "Producer commitments", - "description": "What delivery, documentation, support, monitoring, change, and lifecycle commitments must producers make?" - }, - "consumerResponsibilities": { - "section": "Consumer responsibilities", - "description": "What usage, security, testing, feedback, cost, or compliance responsibilities do consumers accept?" - }, - "architectureImplications": { - "section": "Architecture implications", - "description": "Which requirements must later architecture and implementation decisions satisfy?" + "openCommitments": { + "section": "Open commitments", + "description": "What remains unresolved before architecture or delivery?" } } }, "capabilityArchitectureDecisionCanvas": { "title": "Capability Architecture Decision Canvas", - "purpose": "Compare implementation options and record the selected capability implementation style, enabling platform, rationale, rejected alternatives, assumptions, and risks.", - "howToUse": "Use the shared candidate status control to mark each candidate style as considered, selected, rejected, or not relevant. Compare viable options against consumer needs, reuse potential, coupling, latency, timing, volume, data ownership, consistency, security, trust and location boundaries, reliability, operability, cost, skills, platform fit, governance, discoverability, and lifecycle management.", + "purpose": "Choose how the capability will be delivered using evidence already gathered.", + "howToUse": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", "sections": { - "api": { - "section": "API", - "description": "Where would a governed, reusable programmatic interface best satisfy consumer needs?" - }, - "event": { - "section": "Event", - "description": "Where should consumers react asynchronously to business or data changes?" - }, - "fileBatch": { - "section": "File or batch", - "description": "Where do scheduled, high-volume, delayed, or externally exchanged datasets fit?" - }, - "stream": { - "section": "Stream", - "description": "Where is continuous, replayable, ordered, or low-latency data access needed?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which earlier decisions and constraints shape the implementation choice?" }, - "dataProduct": { - "section": "Data product", - "description": "Where should governed and reusable data be offered as a managed product?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, workflow, application, data product, shared service, human service, or hybrid options remain viable?" }, - "workflow": { - "section": "Workflow", - "description": "Where should orchestration, routing, approvals, or process coordination deliver the capability?" - }, - "sharedService": { - "section": "Shared service", - "description": "Where should a centrally operated service provide reusable business functionality?" - }, - "userFacingApplication": { - "section": "User-facing application", - "description": "Where do consumers need a human-facing experience rather than only a machine interface?" - }, - "directIntegration": { - "section": "Direct integration", - "description": "Where is tightly coupled system-to-system implementation acceptable, and what risks follow?" - }, - "platformNativeFeature": { - "section": "Platform-native feature", - "description": "Can an existing platform capability meet the need without creating unnecessary custom implementation?" - }, - "humanAssistedService": { - "section": "Human-assisted service", - "description": "Which parts require human expertise, judgement, accountability, or exception handling?" - }, - "hybridApproach": { - "section": "Hybrid approach", - "description": "Which combination best delivers the capability?" - }, - "evaluationCriteria": { - "section": "Evaluation criteria", - "description": "How do candidates compare on consumer fit, reuse, coupling, timing, volume, security, reliability, operability, discoverability, cost, governance, skills, and sustainability?" - }, - "selectedStylePlatform": { - "section": "Selected style and platform", + "selectedApproach": { + "section": "Selected approach", "description": "Which implementation style and enabling platform are selected?" }, - "rationaleRejectedAlternatives": { - "section": "Rationale and rejected alternatives", - "description": "Why is the selected approach preferred, and why were alternatives rejected?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "assumptionsRisks": { - "section": "Assumptions and risks", - "description": "What remains uncertain or must be validated before delivery?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" + }, + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "capabilitySolutionDesignCanvas": { "title": "Capability Solution Design Canvas", - "purpose": "Design how consumers access, interact with, receive, or use the capability through the selected implementation style.", - "howToUse": "Use Capability Solution Design Canvas as the primary artifact for this station. Use supporting canvases only where the necessary evidence does not already exist.", + "purpose": "Refine the selected implementation style into a clear consumer-facing capability design.", + "howToUse": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", "sections": { - "selectedImplementationStyle": { - "section": "Selected implementation style", - "description": "Which architecture decision is this design implementing?" - }, - "serviceBoundary": { - "section": "Service boundary", - "description": "What responsibility belongs inside the capability, and what remains outside?" - }, - "consumerInteractionModel": { - "section": "Consumer interaction model", - "description": "How do consumers discover, access, invoke, participate in, or receive the capability?" - }, - "dataBusinessConcepts": { - "section": "Data and business concepts", - "description": "Which concepts, entities, rules, states, and meanings must be shared?" - }, - "contractOrServiceDefinition": { - "section": "Contract or service definition", - "description": "What technical, service, experience, data, workflow, or operational contract defines expected behaviour?" - }, - "responsibilitiesRules": { - "section": "Responsibilities and rules", - "description": "What must consumers, producers, operators, platforms, and supporting teams do?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which earlier journey, value, domain, commitment, and architecture decisions are reused?" }, - "inputsOutputs": { - "section": "Inputs and outputs", - "description": "What information, events, requests, decisions, services, or outcomes enter and leave the capability?" + "boundaryAndInteraction": { + "section": "Boundary and interaction", + "description": "What belongs inside the capability, and how do consumers use it?" }, - "errorsExceptions": { - "section": "Errors and exceptions", - "description": "What failure, invalid-input, unavailable-service, policy, business, and exception conditions must be handled?" + "contractRulesAndOutcomes": { + "section": "Contract, rules, and outcomes", + "description": "What behavior, responsibilities, inputs, outputs, and outcomes are promised?" }, - "lifecycleVersioning": { - "section": "Lifecycle and versioning", - "description": "How will compatibility, change, migration, deprecation, and retirement work?" + "errorsAndSecurity": { + "section": "Errors and security", + "description": "How are exceptions, access, privacy, and trust handled?" }, - "securityPrivacy": { - "section": "Security and privacy", - "description": "What identity, access, confidentiality, consent, retention, audit, and trust controls apply?" + "lifecycleAndSupport": { + "section": "Lifecycle and support", + "description": "How will change, versioning, support, deprecation, and retirement work?" }, "observability": { "section": "Observability", - "description": "What usage, health, quality, value, and consumer signals must be visible?" - }, - "supportModel": { - "section": "Support model", - "description": "How do consumers get help, report issues, and receive status or change communication?" + "description": "What health, usage, quality, value, and consumer signals must be visible?" } } }, "capabilityReadinessOperationsCanvas": { "title": "Capability Readiness & Operations Canvas", - "purpose": "Prepare the operating model for a reusable capability before the formal readiness decision.", - "howToUse": "Use Capability Readiness & Operations Canvas as the primary artifact for this station. Use supporting canvases only where the necessary evidence does not already exist.", + "purpose": "Prepare the minimum operating evidence needed before capability readiness review.", + "howToUse": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Who owns expected value, funding, prioritisation, and release acceptance?" - }, - "capabilityOwner": { - "section": "Capability owner", - "description": "Who owns the capability lifecycle, roadmap, reuse, and consumer outcomes?" - }, - "producerOwner": { - "section": "Producer owner", - "description": "Which producer owner or owners are accountable for delivery, quality, contracts, changes, and producer-side issues?" - }, - "operationalOwner": { - "section": "Operational owner", - "description": "Who owns runtime health, incidents, support, recovery, and runbooks?" - }, - "consumers": { - "section": "Consumers", - "description": "Which consumers are ready, affected, dependent, or still migrating?" - }, - "implementationStyle": { - "section": "Implementation style", - "description": "Which style or hybrid is being operated, and what specific operating implications follow?" - }, - "environments": { - "section": "Environments", - "description": "Which development, test, staging, production, partner, and recovery environments are ready?" + "ownership": { + "section": "Ownership", + "description": "Who owns value, the capability lifecycle, production, operations, support, and changes?" }, - "permissionsCredentials": { - "section": "Permissions and credentials", - "description": "How are access, identities, secrets, certificates, approvals, and reviews managed?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are required environments, access, permissions, and credentials ready?" }, "testEvidence": { "section": "Test evidence", - "description": "What proves functionality, service quality, security, compatibility, resilience, and consumer usability?" + "description": "What proves outcomes, quality, security, compatibility, resilience, and consumer usability?" }, - "serviceExpectations": { - "section": "Service expectations", - "description": "What commitments apply to availability, quality, support, change, and lifecycle?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, usage, value, incidents, consumers, and operators be supported?" }, - "monitoring": { - "section": "Monitoring", - "description": "Which health, usage, quality, value, adoption, cost, and risk signals are monitored?" + "failureAndRecovery": { + "section": "Continuity and recovery", + "description": "How will service continue, degrade safely, recover, or fall back?" }, - "support": { - "section": "Support", - "description": "Who supports consumers and operators, and how are issues escalated?" - }, - "fallbackContinuity": { - "section": "Fallback and continuity", - "description": "How does service continue or degrade safely when the capability is unavailable?" - }, - "changeOwnership": { - "section": "Change ownership", - "description": "Who approves, implements, communicates, and supports changes?" - }, - "documentationRunbooks": { - "section": "Documentation and runbooks", - "description": "Are consumer guidance, service definitions, architecture records, support instructions, and recovery procedures ready?" - }, - "readinessStatus": { + "documentationRisksAndReadiness": { "section": "Readiness status", - "description": "What remains incomplete, conditional, or blocking?" - }, - "knownRisks": { - "section": "Known risks", - "description": "Which risks are mitigated, accepted, deferred, or blocking?" - }, - "improvementBacklog": { - "section": "Improvement backlog", - "description": "What should be improved after release?" + "description": "Are service definitions, runbooks, risks, conditions, and blocking gaps clear?" } } } @@ -2905,30 +1939,6 @@ "purpose": "Mitä arvoa, riskiä sekä operatiivisia, taloudellisia, asiakas-, työntekijä-, vaatimustenmukaisuus- ja strategisia vaikutuksia odotetaan tai on vaakalaudalla?", "howToUse": "Use this to connect expected benefits and consequences to architecture, prioritization, readiness, and proceed-or-stop decisions. Include the impact of not proceeding as well as critical risks and mitigations.", "sections": { - "availabilityRisks": { - "section": "Saatavuuteen liittyvät riskit", - "description": "Mitkä ovat APIn saatavuuteen liittyvät mahdolliset riskit?" - }, - "securityRisks": { - "section": "Tietoturvariskit", - "description": "Mitkä ovat API-rajapintaan liittyvät mahdolliset tietoturvariskit?" - }, - "dataRisks": { - "section": "Tietoriskit", - "description": "Mitkä ovat mahdolliset riskit tiedon eheydelle tai luottamuksellisuudelle?" - }, - "mitigateAvailabilityRisks": { - "section": "Saatavuusriskien vähentäminen", - "description": "Miten API-tarjoaja voi vähentää saatavuuteen liittyviä riskejä?" - }, - "mitigateSecurityRisks": { - "section": "Tietoturvariskien vähentäminen", - "description": "Miten API-tarjoaja voi vähentää tietoturvariskejä?" - }, - "mitigateDataRisks": { - "section": "Tietoriskien vähentäminen", - "description": "Miten API-tarjoaja voi vähentää tietoriskejä?" - }, "expectedBenefits": { "section": "Expected benefits", "description": "What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?" @@ -2996,8 +2006,8 @@ }, "customerJourneyCanvas": { "title": "Asiakaspolkukanvas", - "purpose": "Mikä asiakkaan tai kumppanin polku synnyttää tarpeen kyvykkyydelle tai rajapinnalle?", - "howToUse": "Kuvaa todellinen asiakkaan, kumppanin tai käyttäjän polku, ei API-rajapinnan käyttöä. Polku tuo näkyviin kipupisteet, tavoitteet ja kontekstin, jotka auttavat määrittämään kyvykkyyden ja rajapinnan vaatimukset.", + "purpose": "Millaisen polun mahdollisimman ulkoinen merkityksellinen asiakas kokee, ja mitä siinä pitäisi parantaa?", + "howToUse": "Aloita mahdollisimman ulkoisesta merkityksellisestä asiakkaasta. Kuvaa ensin hänen todellinen polkunsa ja etene vasta sitten kyvykkyyksiin, sisäisiin prosesseihin ja toteutusratkaisuihin.", "sections": { "customerDiscoversNeed": { "section": "Asiakas havaitsee tarpeen", @@ -3030,6 +2040,10 @@ "interactionProcessingRules": { "section": "Vuorovaikutus- ja käsittelysäännöt", "description": "Mitkä roolit, järjestelmät tai säännöt vaikuttavat kulkuun?" + }, + "improvementOpportunities": { + "section": "Parannusmahdollisuudet", + "description": "Mitkä asiakaspolun vaiheet osoittavat, että taustalla olevaa kyvykkyyttä tai prosessia pitäisi luoda, parantaa, automatisoida tai poistaa?" } } }, @@ -3365,887 +2379,424 @@ } }, "automationOpportunityCanvas": { - "title": "Automaation hypoteesikanvas", - "purpose": "Yhdistää valinnaisten tukikanvasten näytön testattavaan automaatiohypoteesiin ennen arkkitehtuuri- tai toimituspäätöksiä.", - "howToUse": "Aloita automaation hypoteesikanvaksesta. Viittaa asiakaspolkuun, arvolupaukseen, toimialueeseen, liiketoimintavaikutukseen, kapasiteettiin tai muuhun näyttöön vain silloin, kun se on olennaista; älä toista näitä kanvaksia tässä.", + "title": "Automation Hypothesis & Validation Canvas", + "purpose": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "howToUse": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", "sections": { "hypothesis": { - "section": "Hypothesis", - "description": "What do we believe automating which work for which actor will achieve? Use the form: We believe automating [work] for [actor] will achieve [outcome]." - }, - "supportingEvidence": { - "section": "Supporting evidence", - "description": "Which Journey, Value Proposition, Business Impact, Capacity, Domain, or other evidence supports this hypothesis? Link or reference existing artifacts instead of repeating them." + "section": "Automation hypothesis", + "description": "What work do we believe should be automated, and what outcome should it achieve?" }, - "automationScope": { - "section": "Scope of automation", - "description": "Which part of the work is being considered for automation now, and what is explicitly outside scope?" - }, - "responsibilityAndSolutionHypothesis": { - "section": "Alustava toteutushypoteesi", - "description": "Mikä on nykyinen oletus siitä, miten automaatio voitaisiin toteuttaa? Tämä on validoitava oletus, ei arkkitehtuuripäätös." + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the hypothesis?" }, "criticalAssumptions": { "section": "Critical assumptions", - "description": "Which assumptions could invalidate value, feasibility, safety, operability, compliance, or adoption?" + "description": "What could make the hypothesis wrong, unsafe, or unworkable?" }, "validationExperiment": { "section": "Validation experiment", - "description": "What is the smallest useful PoC or investigation, what evidence and thresholds decide success, and what stop conditions apply?" + "description": "What is the smallest useful test, evidence threshold, and stop condition?" }, "decision": { "section": "Decision", - "description": "What is the evidence-based decision: supported, revise and retest, redesign the process first, or reject?" - } - } - }, - "humanAutomationResponsibilityCanvas": { - "title": "Human-Automation Responsibility Canvas", - "purpose": "Decide what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "howToUse": "List target process steps and decide the most appropriate performer for each step. Capture required oversight, escalation, and evidence so the solution does not assume every step should be automated.", - "sections": { - "processStep": { - "section": "Process step", - "description": "Which step in the target process is being assigned or reviewed?" - }, - "humanResponsibility": { - "section": "Human responsibility", - "description": "What should a person do, decide, approve, review, correct, or own?" - }, - "ruleOrWorkflowResponsibility": { - "section": "Rule or workflow responsibility", - "description": "What can be handled by deterministic rules, orchestration, routing, reminders, or scheduled workflow?" - }, - "agentOrAiResponsibility": { - "section": "Agent or AI responsibility", - "description": "What judgement, language, classification, generation, planning, or assistance may an agent or AI perform?" - }, - "apiOrSystemResponsibility": { - "section": "API or system responsibility", - "description": "What should be performed through system capability, API, event, connector, file, or direct integration?" - }, - "rpaOrUiAutomationResponsibility": { - "section": "RPA or UI automation responsibility", - "description": "Where is UI automation justified because no suitable system, API, event, connector, or data access path exists?" - }, - "requiredOversight": { - "section": "Required oversight", - "description": "What human supervision, approval, confirmation, monitoring, or review is required before or after the step?" - }, - "escalation": { - "section": "Escalation", - "description": "When should the step stop, ask for help, route to a person, or move to another support path?" - }, - "evidenceOrAuditTrail": { - "section": "Evidence or audit trail", - "description": "What record proves what happened, who or what acted, what data was used, and what decision was made?" + "description": "Proceed, revise, redesign the process, or stop?" } } }, "automationWorkflowCanvas": { - "title": "Automaation työnkulkukanvas", - "purpose": "Suunnittele päästä päähän -automaatiotyönkulun järjestys, tilat, data, käynnistimet, päätökset, vuorovaikutukset, virhepolut ja palautuminen.", - "howToUse": "Käytä ihmisen ja automaation vastuunjaon kanvasta lähtötietona. Keskity siihen, miten työnkulku suoritetaan, vaihtaa tilaa, vaihtaa dataa, käsittelee poikkeuksia, tuottaa näyttöä ja palautuu.", + "title": "Automation Workflow Canvas", + "purpose": "Suunnittele sisäinen työnkulku, jolla valitut asiakas- ja kyvykkyystulokset tuotetaan.", + "howToUse": "Hyödynnä asiakaspolun, arvolupauksen, toimialueen ja validoinnin aiempia tuloksia. Määritä sisäinen työ, jaa se ihmisten ja automaation kesken ja lisää vain toteutuksen kannalta tarvittavat yksityiskohdat.", "sections": { - "trigger": { - "section": "Trigger", - "description": "What event, schedule, user action, message, data change, or manual request starts the automation?" - }, - "inputs": { - "section": "Inputs", - "description": "What data, documents, messages, forms, records, or context are required at the start and during the workflow?" - }, - "workflowStages": { - "section": "Workflow stages and states", - "description": "What are the main workflow stages and states from trigger to completion, including waiting, review, exception, and completion states?" - }, - "decisionsAndRules": { - "section": "Decisions and rules", - "description": "Which deterministic rules, validations, thresholds, policies, or decision points shape the flow?" - }, - "agentActions": { - "section": "Automation actions", - "description": "What may the automation, workflow, rule, agent, integration, API, RPA, or system component do at each relevant stage?" + "selectedCustomerCapabilityOutcomes": { + "section": "Valitut asiakas- ja kyvykkyystulokset", + "description": "Mitkä sovitut asiakas- ja kyvykkyystulokset tämän työnkulun pitää tuottaa?" }, - "systemInteractions": { - "section": "System interactions", - "description": "Which systems, APIs, events, connectors, custom components, files, or screens are called or updated?" + "internalWorkflowSteps": { + "section": "Sisäisen työnkulun vaiheet", + "description": "Mitä sisäistä työtä tarvitaan näiden tulosten tuottamiseksi?" }, - "dataSources": { - "section": "Data sources", - "description": "Which source systems, datasets, records, documents, or knowledge sources are used and trusted?" + "workAllocationHumanControl": { + "section": "Työnjako ja ihmisen valvonta", + "description": "Mikä jää ihmisen tehtäväksi, mikä automatisoidaan ja missä tarvitaan valvontaa tai eskalointia?" }, - "humanTasks": { - "section": "Human checkpoints", - "description": "Where does the responsibility allocation require approval, confirmation, judgement, correction, review, or manual completion?" + "inputsOutputsInteractions": { + "section": "Syötteet, tuotokset ja vuorovaikutukset", + "description": "Mitä tietoja, järjestelmiä ja siirtoja tarvitaan?" }, - "handoffs": { - "section": "Handoffs and queues", - "description": "Where does work move between automation components, people, support teams, systems, queues, or exception paths?" + "decisionsExceptionsRecovery": { + "section": "Päätökset, poikkeukset ja palautuminen", + "description": "Mikä muuttaa työnkulkua, mikä voi epäonnistua ja miten työ palautetaan?" }, - "exceptions": { - "section": "Exceptions", - "description": "What error, missing-data, conflicting-data, timeout, permission, unsafe-action, or business exception scenarios must be handled?" - }, - "retriesAndTimeouts": { - "section": "Retries and timeouts", - "description": "Where are retries, timeout limits, duplicate prevention, idempotency, pause rules, or compensation required?" - }, - "outputs": { - "section": "Outputs", - "description": "What records, decisions, messages, documents, updates, notifications, or outcomes are produced?" - }, - "auditEvidence": { - "section": "Audit evidence", - "description": "What log, trace, approval, run history, input snapshot, output record, or explanation proves correct operation?" - }, - "monitoringPoints": { - "section": "Monitoring points", - "description": "Which run, failure, exception, latency, cost, intervention, quality, safety, or outcome metrics should be observed?" - }, - "recoveryPath": { - "section": "Recovery path", - "description": "How can the process be paused, rolled back, compensated, rerun, corrected, or completed manually?" + "evidenceMonitoring": { + "section": "Todisteet ja seuranta", + "description": "Mikä osoittaa oikean toiminnan ja sen, saavutettiinko tavoiteltu tulos?" } } }, "automationArchitectureDecisionCanvas": { - "title": "Automaation arkkitehtuuripäätöksen kanvas", - "purpose": "Vertaa ja perustele automaatioratkaisun vaihtoehtoiset toteutusmekanismit.", - "howToUse": "Merkitse jokainen ehdokasmekanismi tilaan harkittu, valittu, hylätty tai ei relevantti. Vertaa vain toteuttamiskelpoisia ehdokkaita erikseen ja hybridinä ja perustele suositeltu toteutustapa toteutettavuuden, luotettavuuden, turvallisuuden, ylläpidettävyyden, viiveen, skaalautuvuuden, kustannusten, riippuvuuksien, testattavuuden, havainnoitavuuden, palautettavuuden, osaamisen ja arkkitehtuurisopivuuden perusteella.", + "title": "Automation Architecture Decision Canvas", + "purpose": "Choose the implementation approach using evidence already gathered.", + "howToUse": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", "sections": { - "nativeFeature": { - "section": "Native feature", - "description": "Can an existing system capability solve this step with acceptable reliability, controls, and ownership?" - }, - "workflow": { - "section": "Workflow", - "description": "Where is workflow orchestration, scheduling, routing, approval, notification, or coordination the best fit?" - }, - "rule": { - "section": "Rule", - "description": "Which decisions can be implemented as deterministic business rules, policy checks, validations, or calculations?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which requirements, capacity, location, impact, and responsibility decisions constrain the choice?" }, - "agent": { - "section": "Agent", - "description": "Where could an agent or AI safely add judgement, language understanding, generation, planning, or assistance?" + "viableOptions": { + "section": "Viable options", + "description": "Which human, workflow, rule, agent, API, connector, custom, or UI automation options remain viable?" }, - "connector": { - "section": "Connector", - "description": "Which low-code, platform, SaaS, file, message, or data connectors are viable?" - }, - "api": { - "section": "API", - "description": "Where is an API call the best fit for reliable, governed, testable system interaction?" - }, - "event": { - "section": "Event", - "description": "Where should the solution react to, publish, or consume events?" - }, - "customCode": { - "section": "Custom code", - "description": "Where is custom code justified because standard capabilities are insufficient or too risky?" - }, - "rpa": { - "section": "RPA", - "description": "Where is desktop or UI automation justified, and what fragility or recovery controls are required?" - }, - "humanTask": { - "section": "Human task", - "description": "Which steps should remain human because of judgement, accountability, risk, consent, policy, or exception handling?" - }, - "feasibilityReliabilitySecurity": { - "section": "Feasibility, reliability, security", - "description": "How do candidates compare on technical feasibility, expected reliability, identity, authorization, data exposure, and control strength?" - }, - "maintainabilityScalabilityCost": { - "section": "Maintainability, scalability, cost", - "description": "How do candidates compare on change effort, operating cost, licence cost, transaction volume, peak load, and lifecycle maintenance?" - }, - "latencyObservabilityRecoverability": { - "section": "Latency, observability, recoverability", - "description": "How do candidates compare on timing needs, monitoring, logs, traceability, retry, compensation, and manual recovery?" - }, - "skillsVendorFit": { - "section": "Skills, vendor dependency, architectural fit", - "description": "What skills, ownership, platform dependencies, governance constraints, and architecture standards affect the decision?" - }, - "recommendedHybridApproach": { - "section": "Recommended hybrid approach", - "description": "Which combination of people, rules, workflows, agents, systems, APIs, events, custom code, and UI automation should be used?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style or hybrid is selected?" }, "decisionRationale": { "section": "Decision rationale", - "description": "Why is this approach preferred over the alternatives, and what evidence supports the decision?" + "description": "Why does the selected approach fit best?" }, - "openQuestionsAndRisks": { - "section": "Open questions and risks", - "description": "Which assumptions, risks, dependencies, or unresolved constraints must be validated before delivery or release?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" + }, + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "automationReadinessOperationsCanvas": { - "title": "Automaation valmius- ja operointikanvas", - "purpose": "Valmistele toimintamalli turvallisesti julkaistavalle, tuetulle, valvotulle ja palautettavalle automaatiolle.", - "howToUse": "Käytä tätä toimituksen aikana omistajuuden, ympäristöjen, käyttöoikeuksien, näytön, valvonnan, tuen, varamenettelyn, palautuksen, runbookien, tunnettujen riskien ja julkaisun valmiustilan valmisteluun. Käytä myöhemmin valmiustarkistuslistaa muodollisena porttina.", + "title": "Automation Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before readiness review.", + "howToUse": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Who accepts business value, process impact, residual risk, and release timing?" - }, - "operationalOwner": { - "section": "Operational owner", - "description": "Who owns runtime supervision, incidents, support, runbooks, changes, and recovery?" - }, - "users": { - "section": "Users", - "description": "Which users, operators, approvers, support teams, or process participants are affected?" - }, - "permissions": { - "section": "Permissions", - "description": "What human, service, system, data, role, and approval permissions are required and approved?" - }, - "credentials": { - "section": "Credentials", - "description": "How are credentials, secrets, certificates, tokens, delegated access, and service identities managed?" + "ownership": { + "section": "Ownership", + "description": "Who owns business outcomes, operations, support, and changes?" }, - "environments": { - "section": "Environments", - "description": "Which development, test, staging, production, desktop, cloud, or platform environments are used?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, permissions, credentials, and identities ready?" }, "testEvidence": { "section": "Test evidence", - "description": "What proves functional correctness, rule behavior, integration behavior, agent behavior, permissions, performance, and exceptions?" + "description": "What proves correct, safe, and reliable behavior?" }, - "exceptionHandling": { - "section": "Exception handling", - "description": "How are errors, missing data, unsafe actions, failed runs, retries, timeouts, and handoffs handled?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, incidents, users, and operators be supported?" }, - "monitoring": { - "section": "Monitoring", - "description": "Which run, failure, exception, latency, cost, intervention, value, safety, and outcome signals are monitored?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will exceptions, fallback, rollback, and manual recovery work?" }, - "support": { - "section": "Support", - "description": "Who supports users and operators, how are incidents raised, and what service expectations apply?" - }, - "manualFallback": { - "section": "Manual fallback", - "description": "How can work continue manually if the automation is paused, unavailable, incorrect, or unsafe?" - }, - "rollback": { - "section": "Rollback", - "description": "How can changes, actions, data updates, releases, or workflow versions be reversed or compensated?" - }, - "documentation": { - "section": "Documentation", - "description": "What operating instructions, design records, architecture decisions, user guidance, and runbooks are ready?" - }, - "deploymentDecision": { - "section": "Julkaisuvalmiuden tila", - "description": "Mikä on vielä keskeneräistä, ehdollista tai estävää ennen muodollista valmiuspäätöstä?" - }, - "knownRisks": { - "section": "Known risks", - "description": "Which risks are accepted, mitigated, deferred, or blocking release?" - }, - "improvementBacklog": { - "section": "Improvement backlog", - "description": "Which improvements, unresolved assumptions, PoC findings, and future enhancements should be prioritized next?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are documentation, risks, conditions, and blocking gaps clear?" } } }, "integrationCapabilityHypothesisCanvas": { - "title": "Integraatiokyvykkyyden hypoteesikanvas", - "purpose": "Priorisoi uudelleenkäytettävä integraatiokyvykkyyshypoteesi yhdistämällä kuluttaja-, arvo-, domain-, omistajuus-, uudelleenkäyttö- ja elinkelpoisuusnäyttö selkeään rajaukseen, oletuksiin, validointiaskeleeseen ja jatka-tai-pysäytä-päätökseen.", - "howToUse": "Aloita tästä ennen arkkitehtuurin valintaa. Viittaa journey-, arvolupaus-, domain-, liiketoimintamalli-, vaikutus-, kapasiteetti- tai muuhun näyttöön vain silloin, kun se tukee hypoteesia.", + "title": "Integration Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable integration capability should proceed.", + "howToUse": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", "sections": { - "hypothesis": { - "section": "Integraatiokyvykkyyden hypoteesi", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Integraatiokyvykkyyden hypoteesi pitää kirjata?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed integration capability and reuse scope are being tested?" }, - "consumersAndReuseScope": { - "section": "Tarkoitetut kuluttajat ja uudelleenkäytön rajaus", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tarkoitetut kuluttajat ja uudelleenkäytön rajaus pitää kirjata?" - }, - "providerAndOwner": { - "section": "Tarjoaja ja omistaja", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tarjoaja ja omistaja pitää kirjata?" - }, - "supportingEvidence": { - "section": "Tukeva näyttö", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tukeva näyttö pitää kirjata?" - }, - "implementationStyleHypothesis": { - "section": "Alustava toteutustyylihypoteesi", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Alustava toteutustyylihypoteesi pitää kirjata?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { - "section": "Kriittiset oletukset", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Kriittiset oletukset pitää kirjata?" + "section": "Critical assumptions", + "description": "What could invalidate value, reuse, ownership, feasibility, or adoption?" }, - "validationExperiment": { - "section": "Validointikokeilu", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Validointikokeilu pitää kirjata?" + "validationStep": { + "section": "Validation step", + "description": "What is the smallest useful validation and success threshold?" }, "decision": { - "section": "Päätös", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Päätös pitää kirjata?" + "section": "Decision", + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "integrationConsumerProviderRequirementsCanvas": { - "title": "Integraation kuluttaja- ja tarjoajavaatimusten kanvas", - "purpose": "Kuvaa, mitä kuluttavat järjestelmät, tiimit, tuottajat, tarjoajat ja operoijat tarvitsevat ennen integraation toteutustavan valintaa tai suunnittelua.", - "howToUse": "Tee näkyväksi onboarding, pääsy, ympäristöt, identiteetti, yhteensopivuus, palveluodotukset, datan laatu, tuki ja palautumisvaatimukset.", + "title": "Integration Consumer & Provider Commitments Canvas", + "purpose": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "howToUse": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", "sections": { - "consumerSystemsAndTeams": { - "section": "Kuluttajajärjestelmät ja tiimit", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Kuluttajajärjestelmät ja tiimit pitää kirjata?" - }, - "providerResponsibilities": { - "section": "Tarjoajan vastuut", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tarjoajan vastuut pitää kirjata?" - }, - "interactionAndDataNeeds": { - "section": "Vuorovaikutus- ja datatarpeet", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Vuorovaikutus- ja datatarpeet pitää kirjata?" + "selectedPartiesAndUseCases": { + "section": "Selected parties and use cases", + "description": "Which producers, providers, consumers, and use cases are covered?" }, - "onboardingAndAccess": { - "section": "Onboarding ja pääsy", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Onboarding ja pääsy pitää kirjata?" - }, - "environmentsAndTestAccess": { - "section": "Ympäristöt ja testipääsy", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Ympäristöt ja testipääsy pitää kirjata?" - }, - "credentialsAndIdentity": { - "section": "Tunnistetiedot ja identiteetti", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tunnistetiedot ja identiteetti pitää kirjata?" - }, - "compatibilityAndVersioning": { - "section": "Yhteensopivuus ja versiointi", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Yhteensopivuus ja versiointi pitää kirjata?" + "providerCommitments": { + "section": "Provider commitments", + "description": "What will providers deliver, maintain, monitor, and support?" }, - "serviceExpectations": { - "section": "Palveluodotukset", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Palveluodotukset pitää kirjata?" + "consumerCommitments": { + "section": "Consumer commitments", + "description": "What must consumers test, protect, operate, and communicate?" }, - "dataQualityAndObservability": { - "section": "Datan laatu ja havainnoitavuus", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Datan laatu ja havainnoitavuus pitää kirjata?" + "accessAndValidationAgreement": { + "section": "Access and validation", + "description": "How will access, environments, credentials, and conformance be handled?" }, - "supportAndFailureHandling": { - "section": "Tuki ja virheenkäsittely", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tuki ja virheenkäsittely pitää kirjata?" + "failureAndRecoveryAgreement": { + "section": "Failure and recovery", + "description": "Who handles failures, replay, duplicates, reconciliation, and recovery?" }, - "replayReconciliationRecovery": { - "section": "Replay, täsmäytys ja palautuminen", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Replay, täsmäytys ja palautuminen pitää kirjata?" + "changeAndLifecycleAgreement": { + "section": "Change and lifecycle", + "description": "How will compatibility, migration, notice, deprecation, and retirement work?" } } }, "integrationArchitectureDecisionCanvas": { - "title": "Integraation arkkitehtuuripäätöksen kanvas", - "purpose": "Vertaa ja perustele integraation toteutustyylit, alustakyvykkyydet, governance-rajoitteet ja hylätyt vaihtoehdot.", - "howToUse": "Käytä yhteistä ehdokasstatus-valintaa merkitäksesi jokaisen ehdokastyylin tarkastelluksi, valituksi, hylätyksi tai ei-relevantiksi. Vertaa toteuttamiskelpoisia vaihtoehtoja ajoituksen, kytkeytymisen, datan omistajuuden, konsistenssin, luotettavuuden, turvallisuuden, ylläpidettävyyden, havainnoitavuuden, palautumisen, kustannusten, governancen ja osaamisen perusteella.", + "title": "Integration Architecture Decision Canvas", + "purpose": "Choose the integration style and platform using evidence already gathered.", + "howToUse": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", "sections": { - "synchronousApi": { - "section": "Synkroninen API", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Synkroninen API pitää kirjata?" - }, - "eventDriven": { - "section": "Asynkroninen tapahtuma", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Asynkroninen tapahtuma pitää kirjata?" - }, - "messagingQueue": { - "section": "Viestitys tai jono", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Viestitys tai jono pitää kirjata?" - }, - "batchFileExchange": { - "section": "Batch- tai tiedostovaihto", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Batch- tai tiedostovaihto pitää kirjata?" - }, - "stream": { - "section": "Stream", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Stream pitää kirjata?" - }, - "etlElt": { - "section": "ETL tai ELT", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa ETL tai ELT pitää kirjata?" - }, - "dataProduct": { - "section": "Datatuote", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Datatuote pitää kirjata?" - }, - "directDatabase": { - "section": "Suora tietokantaintegraatio", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Suora tietokantaintegraatio pitää kirjata?" - }, - "sharedPlatform": { - "section": "Yhteinen integraatioalusta", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Yhteinen integraatioalusta pitää kirjata?" - }, - "pointToPoint": { - "section": "Point-to-point", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Point-to-point pitää kirjata?" - }, - "managedConnector": { - "section": "Hallittu connector", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Hallittu connector pitää kirjata?" - }, - "customIntegration": { - "section": "Räätälöity integraatio", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Räätälöity integraatio pitää kirjata?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which commitments, capacity, location, impact, and domain decisions constrain the choice?" }, - "hybridApproach": { - "section": "Hybridiratkaisu", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Hybridiratkaisu pitää kirjata?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, messaging, file, stream, data, connector, platform, or custom options remain viable?" }, - "evaluationCriteria": { - "section": "Arviointikriteerit", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Arviointikriteerit pitää kirjata?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which integration style, platform, or hybrid is selected?" }, - "selectedStyleAndPlatform": { - "section": "Valittu tyyli ja alusta", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Valittu tyyli ja alusta pitää kirjata?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "rationaleAndRejectedAlternatives": { - "section": "Perustelu ja hylätyt vaihtoehdot", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Perustelu ja hylätyt vaihtoehdot pitää kirjata?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "openRisksAndAssumptions": { - "section": "Avoimet riskit ja oletukset", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Avoimet riskit ja oletukset pitää kirjata?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "integrationReadinessOperationsCanvas": { - "title": "Integraation valmius- ja operointikanvas", - "purpose": "Valmistele toimintamalli turvallisesti julkaistavalle, tuetulle, valvotulle, palautettavalle ja uudelleenkäytettävälle integraatiokyvykkyydelle.", - "howToUse": "Käytä tätä toimituksen aikana omistajuuden, ympäristöjen, tunnistetietojen, käyttöönoton, seurannan, tuen, retryn, replayn, täsmäytyksen, fallbackin, rollbackin, incidentien, testinäytön, riskien ja valmiustilan valmisteluun.", + "title": "Integration Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before integration readiness review.", + "howToUse": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Business owner pitää kirjata?" - }, - "integrationOwner": { - "section": "Integraation omistaja", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Integraation omistaja pitää kirjata?" - }, - "producerOwners": { - "section": "Tuottajaomistajat", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tuottajaomistajat pitää kirjata?" - }, - "consumerOwners": { - "section": "Kuluttajaomistajat", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Kuluttajaomistajat pitää kirjata?" - }, - "platformOwner": { - "section": "Alustan omistaja", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Alustan omistaja pitää kirjata?" - }, - "environments": { - "section": "Ympäristöt", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Ympäristöt pitää kirjata?" + "ownership": { + "section": "Ownership", + "description": "Who owns business, integration, producer, consumer, platform, and incident responsibilities?" }, - "credentials": { - "section": "Tunnistetiedot", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tunnistetiedot pitää kirjata?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, credentials, connectivity, permissions, and sequencing ready?" }, - "deployment": { - "section": "Deployment", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Deployment pitää kirjata?" - }, - "monitoring": { - "section": "Seuranta", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Seuranta pitää kirjata?" - }, - "support": { - "section": "Tuki", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Tuki pitää kirjata?" - }, - "retryReplay": { - "section": "Retry ja replay", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Retry ja replay pitää kirjata?" - }, - "reconciliation": { - "section": "Täsmäytys", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Täsmäytys pitää kirjata?" - }, - "fallbackRollback": { - "section": "Fallback ja rollback", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Fallback ja rollback pitää kirjata?" - }, - "incidentOwnership": { - "section": "Incident-omistajuus", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Incident-omistajuus pitää kirjata?" + "testEvidence": { + "section": "Test evidence", + "description": "What proves contract, mapping, compatibility, quality, resilience, and recovery?" }, - "testEvidenceKnownRisks": { - "section": "Testinäyttö ja tunnetut riskit", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Testinäyttö ja tunnetut riskit pitää kirjata?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will producers, consumers, platforms, incidents, and service questions be supported?" }, - "readinessStatus": { - "section": "Valmiustila", - "description": "Mitä tietoja, näyttöä, päätöksiä ja avoimia asioita kohdassa Valmiustila pitää kirjata?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will retry, replay, duplicates, reconciliation, fallback, and compensation work?" }, - "documentationDependenciesChangeReadiness": { - "section": "Dokumentaatio, riippuvuudet ja muutosvalmius", - "description": "Ovatko sopimukset, mäppäykset, runbookit, riippuvuudet, migraatio-ohjeet, deployment-järjestys, cutover, taaksepäin yhteensopivuus, versio-omistajuus ja muutosvastuut valmiit?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are contracts, runbooks, dependencies, risks, conditions, and blocking gaps clear?" } } }, "integrationSolutionDesignCanvas": { - "title": "Integraatioratkaisun suunnittelukanvas", - "purpose": "Kokoaa integraatiosuunnitelman eri toteutustyylien yli, mukaan lukien sopimukset, skeemat, tietorakenteet, mäppäykset, toimituskäyttäytyminen, turvallisuus, virheet, havainnoitavuus, täsmäytys ja versiointi.", - "howToUse": "Käytä tätä ensisijaisena ratkaisusuunnittelun artefaktina arkkitehtuuripäätöksen jälkeen. Käytä Interaction Canvas-, REST-, Event-, GraphQL-, tiedosto-, stream-, datatuote- tai viestintäresursseja vain ehdollisena syventävänä tukena.", + "title": "Integration Solution Design Canvas", + "purpose": "Refine the selected architecture into an implementable integration design.", + "howToUse": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", "sections": { - "selectedIntegrationStyle": { - "section": "Valittu integraatiotyyli", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Valittu integraatiotyyli pitää kirjata?" - }, - "producerAndConsumer": { - "section": "Tuottaja ja kuluttaja", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Tuottaja ja kuluttaja pitää kirjata?" - }, - "contractAndSchema": { - "section": "Sopimus ja skeema", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Sopimus ja skeema pitää kirjata?" - }, - "mappingsAndTransformations": { - "section": "Mäppäykset ja transformaatiot", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Mäppäykset ja transformaatiot pitää kirjata?" - }, - "interactionDeliveryPattern": { - "section": "Vuorovaikutus- tai toimitusmalli", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Vuorovaikutus- tai toimitusmalli pitää kirjata?" - }, - "identityAndSecurity": { - "section": "Identiteetti ja turvallisuus", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Identiteetti ja turvallisuus pitää kirjata?" - }, - "errorRetryReplay": { - "section": "Virhemalli, retry ja replay", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Virhemalli, retry ja replay pitää kirjata?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which architecture, domain, interaction, and commitment decisions are reused?" }, - "correlationMetadata": { - "section": "Korrelaatio ja metadata", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Korrelaatio ja metadata pitää kirjata?" + "contractAndModel": { + "section": "Contract and model", + "description": "What contract, schema, data model, and version define the integration?" }, - "reconciliationRules": { - "section": "Täsmäytyssäännöt", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Täsmäytyssäännöt pitää kirjata?" + "mappingAndDelivery": { + "section": "Mapping and delivery", + "description": "What transformations, delivery pattern, and metadata are required?" }, - "observability": { - "section": "Havainnoitavuus", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Havainnoitavuus pitää kirjata?" + "errorsAndRecovery": { + "section": "Errors and recovery", + "description": "How are failures, retries, replay, duplicates, and reconciliation handled?" }, - "versioningEvolution": { - "section": "Versiointi ja kehitys", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Versiointi ja kehitys pitää kirjata?" + "securityAndTrust": { + "section": "Security and trust", + "description": "What identity, access, privacy, and trust controls apply?" }, - "canonicalConsumerSpecificModel": { - "section": "Kanoninen vs. kuluttajakohtainen malli", - "description": "Mitä suunnittelupäätöksiä, sääntöjä, näyttöä ja avoimia asioita kohdassa Kanoninen vs. kuluttajakohtainen malli pitää kirjata?" + "observabilityAndEvolution": { + "section": "Observability and evolution", + "description": "How will the integration be monitored, changed, migrated, and deprecated?" } } }, "capabilityHypothesisCanvas": { - "title": "Kyvykkyyshypoteesin kanvas", - "purpose": "Priorisoi uudelleenkäytettävä digitaalinen kyvykkyyshypoteesi yhdistämällä kuluttaja-, arvo-, domain-, omistajuus-, elinkelpoisuus- ja uudelleenkäyttönäyttö selkeään rajaukseen, oletuksiin, validointiaskeleeseen ja päätökseen.", - "howToUse": "Mitä päätöksiä, näyttöä ja avoimia asioita kohdassa Kyvykkyyshypoteesin kanvas pitää kirjata?", + "title": "Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable digital capability should proceed.", + "howToUse": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", "sections": { - "hypothesis": { - "section": "Kyvykkyyshypoteesi", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Kyvykkyyshypoteesi pitää kirjata?" - }, - "targetConsumersUseCases": { - "section": "Kohdekuluttajat ja käyttötapaukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Kohdekuluttajat ja käyttötapaukset pitää kirjata?" - }, - "reusableScope": { - "section": "Tarkoitettu uudelleenkäytön rajaus", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tarkoitettu uudelleenkäytön rajaus pitää kirjata?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed capability and reusable scope are being tested?" }, - "supportingEvidence": { - "section": "Tukeva näyttö", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tukeva näyttö pitää kirjata?" - }, - "expectedOutcomes": { - "section": "Odotetut tulokset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Odotetut tulokset pitää kirjata?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { - "section": "Kriittiset oletukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Kriittiset oletukset pitää kirjata?" + "section": "Critical assumptions", + "description": "What could invalidate value, reuse, ownership, sustainability, or adoption?" }, "minimumValidation": { - "section": "Vähimmäisvalidaatio", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Vähimmäisvalidaatio pitää kirjata?" + "section": "Minimum validation", + "description": "What is the smallest useful validation and success threshold?" }, "decision": { - "section": "Päätös", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Päätös pitää kirjata?" + "section": "Decision", + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "capabilityConsumerProducerRequirementsCanvas": { - "title": "Kuluttaja- ja tuottajavaatimusten kanvas", - "purpose": "Kuvaa, mitä kuluttajat, tuottajat, omistajat, operoijat ja tukitiimit tarvitsevat uudelleenkäytettävältä kyvykkyydeltä ennen toteutustyylin valintaa tai suunnittelua.", - "howToUse": "Mitä päätöksiä, näyttöä ja avoimia asioita kohdassa Kuluttaja- ja tuottajavaatimusten kanvas pitää kirjata?", + "title": "Capability Consumer & Producer Commitments Canvas", + "purpose": "Agree mutual commitments for providing and consuming a reusable capability.", + "howToUse": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", "sections": { - "intendedConsumersContexts": { - "section": "Tarkoitetut kuluttajat ja kontekstit", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tarkoitetut kuluttajat ja kontekstit pitää kirjata?" + "selectedConsumersAndUseCases": { + "section": "Selected consumers and use cases", + "description": "Which consumers and usage contexts are covered?" }, - "capabilityOwnerProducerResponsibilities": { - "section": "Kyvykkyyden omistaja ja tuottajavastuut", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Kyvykkyyden omistaja ja tuottajavastuut pitää kirjata?" + "ownerAndProducerCommitments": { + "section": "Owner and producer commitments", + "description": "What will owners and producers provide, maintain, monitor, and support?" }, - "discoveryEvaluation": { - "section": "Löydettävyys ja arviointi", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Löydettävyys ja arviointi pitää kirjata?" - }, - "accessOnboarding": { - "section": "Pääsy ja onboarding", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Pääsy ja onboarding pitää kirjata?" - }, - "serviceExpectations": { - "section": "Palveluodotukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Palveluodotukset pitää kirjata?" - }, - "qualityAvailability": { - "section": "Laatu- ja saatavuusodotukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Laatu- ja saatavuusodotukset pitää kirjata?" - }, - "changeLifecycle": { - "section": "Muutos- ja elinkaariodotukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Muutos- ja elinkaariodotukset pitää kirjata?" - }, - "supportIncidentCommunication": { - "section": "Tuki ja incident-viestintä", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tuki ja incident-viestintä pitää kirjata?" - }, - "operationalGovernanceConstraints": { - "section": "Operatiiviset ja governance-reunaehdot", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Operatiiviset ja governance-reunaehdot pitää kirjata?" + "consumerResponsibilities": { + "section": "Consumer responsibilities", + "description": "What must consumers do for appropriate use, access, testing, and feedback?" }, - "producerCommitments": { - "section": "Tuottajan sitoumukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tuottajan sitoumukset pitää kirjata?" + "accessAndOnboardingAgreement": { + "section": "Access and onboarding", + "description": "What discovery, approval, testing, and onboarding path is agreed?" }, - "consumerResponsibilities": { - "section": "Kuluttajan vastuut", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Kuluttajan vastuut pitää kirjata?" + "serviceAndLifecycleAgreement": { + "section": "Service and lifecycle", + "description": "What service, change, deprecation, and retirement commitments are agreed?" }, - "architectureImplications": { - "section": "Arkkitehtuurivaikutukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Arkkitehtuurivaikutukset pitää kirjata?" + "openCommitments": { + "section": "Open commitments", + "description": "What remains unresolved before architecture or delivery?" } } }, "capabilityArchitectureDecisionCanvas": { - "title": "Kyvykkyyden arkkitehtuuripäätöksen kanvas", - "purpose": "Vertaa toteutusvaihtoehtoja ja kirjaa kyvykkyyden valittu toteutustyyli, mahdollistava alusta, perustelu, hylätyt vaihtoehdot, oletukset ja riskit.", - "howToUse": "Käytä yhteistä ehdokasstatus-valintaa merkitäksesi jokaisen ehdokastyylin tarkastelluksi, valituksi, hylätyksi tai ei-relevantiksi. Vertaa vaihtoehtoja kuluttajatarpeiden, uudelleenkäytön, kytkeytymisen, latenssin, ajoituksen, volyymin, datan omistajuuden, konsistenssin, turvallisuuden, luottamus- ja sijaintirajojen, luotettavuuden, operoitavuuden, kustannusten, osaamisen, alustasopivuuden, governancen, löydettävyyden ja elinkaarenhallinnan perusteella.", + "title": "Capability Architecture Decision Canvas", + "purpose": "Choose how the capability will be delivered using evidence already gathered.", + "howToUse": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", "sections": { - "api": { - "section": "API", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa API pitää kirjata?" - }, - "event": { - "section": "Tapahtuma", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tapahtuma pitää kirjata?" - }, - "fileBatch": { - "section": "Tiedosto tai batch", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tiedosto tai batch pitää kirjata?" - }, - "stream": { - "section": "Stream", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Stream pitää kirjata?" - }, - "dataProduct": { - "section": "Datatuote", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Datatuote pitää kirjata?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which earlier decisions and constraints shape the implementation choice?" }, - "workflow": { - "section": "Workflow", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Workflow pitää kirjata?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, workflow, application, data product, shared service, human service, or hybrid options remain viable?" }, - "sharedService": { - "section": "Jaettu palvelu", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Jaettu palvelu pitää kirjata?" - }, - "userFacingApplication": { - "section": "Käyttäjälle näkyvä sovellus", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Käyttäjälle näkyvä sovellus pitää kirjata?" - }, - "directIntegration": { - "section": "Suora integraatio", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Suora integraatio pitää kirjata?" - }, - "platformNativeFeature": { - "section": "Alustan natiivi toiminto", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Alustan natiivi toiminto pitää kirjata?" - }, - "humanAssistedService": { - "section": "Ihmisen tukema palvelu", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Ihmisen tukema palvelu pitää kirjata?" - }, - "hybridApproach": { - "section": "Hybridiratkaisu", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Hybridiratkaisu pitää kirjata?" - }, - "evaluationCriteria": { - "section": "Arviointikriteerit", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Arviointikriteerit pitää kirjata?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style and enabling platform are selected?" }, - "selectedStylePlatform": { - "section": "Valittu tyyli ja alusta", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Valittu tyyli ja alusta pitää kirjata?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "rationaleRejectedAlternatives": { - "section": "Perustelu ja hylätyt vaihtoehdot", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Perustelu ja hylätyt vaihtoehdot pitää kirjata?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "assumptionsRisks": { - "section": "Oletukset ja riskit", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Oletukset ja riskit pitää kirjata?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "capabilitySolutionDesignCanvas": { - "title": "Kyvykkyysratkaisun suunnittelukanvas", - "purpose": "Suunnittele, miten kuluttajat pääsevät kyvykkyyteen, ovat vuorovaikutuksessa sen kanssa, vastaanottavat sen tai käyttävät sitä valitun toteutustyylin kautta.", - "howToUse": "Mitä päätöksiä, näyttöä ja avoimia asioita kohdassa Kyvykkyysratkaisun suunnittelukanvas pitää kirjata?", + "title": "Capability Solution Design Canvas", + "purpose": "Refine the selected implementation style into a clear consumer-facing capability design.", + "howToUse": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", "sections": { - "selectedImplementationStyle": { - "section": "Valittu toteutustyyli", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Valittu toteutustyyli pitää kirjata?" - }, - "serviceBoundary": { - "section": "Palveluraja", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Palveluraja pitää kirjata?" - }, - "consumerInteractionModel": { - "section": "Kuluttajan vuorovaikutusmalli", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Kuluttajan vuorovaikutusmalli pitää kirjata?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which earlier journey, value, domain, commitment, and architecture decisions are reused?" }, - "dataBusinessConcepts": { - "section": "Data- ja liiketoimintakäsitteet", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Data- ja liiketoimintakäsitteet pitää kirjata?" - }, - "contractOrServiceDefinition": { - "section": "Sopimus tai palvelumäärittely", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Sopimus tai palvelumäärittely pitää kirjata?" - }, - "responsibilitiesRules": { - "section": "Vastuut ja säännöt", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Vastuut ja säännöt pitää kirjata?" - }, - "inputsOutputs": { - "section": "Syötteet ja tuotokset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Syötteet ja tuotokset pitää kirjata?" + "boundaryAndInteraction": { + "section": "Boundary and interaction", + "description": "What belongs inside the capability, and how do consumers use it?" }, - "errorsExceptions": { - "section": "Virheet ja poikkeukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Virheet ja poikkeukset pitää kirjata?" + "contractRulesAndOutcomes": { + "section": "Contract, rules, and outcomes", + "description": "What behavior, responsibilities, inputs, outputs, and outcomes are promised?" }, - "lifecycleVersioning": { - "section": "Elinkaari ja versiointi", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Elinkaari ja versiointi pitää kirjata?" + "errorsAndSecurity": { + "section": "Errors and security", + "description": "How are exceptions, access, privacy, and trust handled?" }, - "securityPrivacy": { - "section": "Turvallisuus ja tietosuoja", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Turvallisuus ja tietosuoja pitää kirjata?" + "lifecycleAndSupport": { + "section": "Lifecycle and support", + "description": "How will change, versioning, support, deprecation, and retirement work?" }, "observability": { - "section": "Havainnoitavuus", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Havainnoitavuus pitää kirjata?" - }, - "supportModel": { - "section": "Tukimalli", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tukimalli pitää kirjata?" + "section": "Observability", + "description": "What health, usage, quality, value, and consumer signals must be visible?" } } }, "capabilityReadinessOperationsCanvas": { - "title": "Kyvykkyyden valmius- ja operointikanvas", - "purpose": "Valmistele uudelleenkäytettävän kyvykkyyden toimintamalli ennen muodollista valmiuspäätöstä.", - "howToUse": "Mitä päätöksiä, näyttöä ja avoimia asioita kohdassa Kyvykkyyden valmius- ja operointikanvas pitää kirjata?", + "title": "Capability Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before capability readiness review.", + "howToUse": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Business owner pitää kirjata?" - }, - "capabilityOwner": { - "section": "Kyvykkyyden omistaja", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Kyvykkyyden omistaja pitää kirjata?" - }, - "producerOwner": { - "section": "Tuottajaomistaja", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tuottajaomistaja pitää kirjata?" - }, - "operationalOwner": { - "section": "Operatiivinen omistaja", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Operatiivinen omistaja pitää kirjata?" - }, - "consumers": { - "section": "Kuluttajat", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Kuluttajat pitää kirjata?" - }, - "implementationStyle": { - "section": "Toteutustyyli", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Toteutustyyli pitää kirjata?" + "ownership": { + "section": "Ownership", + "description": "Who owns value, the capability lifecycle, production, operations, support, and changes?" }, - "environments": { - "section": "Ympäristöt", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Ympäristöt pitää kirjata?" - }, - "permissionsCredentials": { - "section": "Oikeudet ja tunnistetiedot", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Oikeudet ja tunnistetiedot pitää kirjata?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are required environments, access, permissions, and credentials ready?" }, "testEvidence": { - "section": "Testinäyttö", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Testinäyttö pitää kirjata?" - }, - "serviceExpectations": { - "section": "Palveluodotukset", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Palveluodotukset pitää kirjata?" - }, - "monitoring": { - "section": "Seuranta", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Seuranta pitää kirjata?" - }, - "support": { - "section": "Tuki", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tuki pitää kirjata?" - }, - "fallbackContinuity": { - "section": "Fallback ja jatkuvuus", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Fallback ja jatkuvuus pitää kirjata?" - }, - "changeOwnership": { - "section": "Muutoksen omistajuus", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Muutoksen omistajuus pitää kirjata?" - }, - "documentationRunbooks": { - "section": "Dokumentaatio ja runbookit", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Dokumentaatio ja runbookit pitää kirjata?" + "section": "Test evidence", + "description": "What proves outcomes, quality, security, compatibility, resilience, and consumer usability?" }, - "readinessStatus": { - "section": "Valmiustila", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Valmiustila pitää kirjata?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, usage, value, incidents, consumers, and operators be supported?" }, - "knownRisks": { - "section": "Tunnetut riskit", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Tunnetut riskit pitää kirjata?" + "failureAndRecovery": { + "section": "Continuity and recovery", + "description": "How will service continue, degrade safely, recover, or fall back?" }, - "improvementBacklog": { - "section": "Parannusbacklog", - "description": "Mitä konkreettisia päätöksiä, näyttöä, vastuita, riskejä ja seuraavia askeleita kohdassa Parannusbacklog pitää kirjata?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are service definitions, runbooks, risks, conditions, and blocking gaps clear?" } } } @@ -4322,30 +2873,6 @@ "purpose": "Quelle valeur, quels risques et quels impacts opérationnels, financiers, clients, employés, conformité et stratégiques sont attendus ou en jeu?", "howToUse": "Use this to connect expected benefits and consequences to architecture, prioritization, readiness, and proceed-or-stop decisions. Include the impact of not proceeding as well as critical risks and mitigations.", "sections": { - "availabilityRisks": { - "section": "Risques de disponibilité", - "description": "Quels sont les risques potentiels pour la disponibilité de l’API?" - }, - "securityRisks": { - "section": "Risques de sécurité", - "description": "Quels sont les risques de sécurité potentiels associés à l’API?" - }, - "dataRisks": { - "section": "Risques liés aux données", - "description": "Quels sont les risques potententiels pour l'intégrité ou la protection des données?" - }, - "mitigateAvailabilityRisks": { - "section": "Atténuer les risques de disponibilité", - "description": "Comment le fournisseur d’API peut-il atténuer les risques de disponibilité?" - }, - "mitigateSecurityRisks": { - "section": "Atténuer les risques de sécurité", - "description": "Comment le fournisseur d’API peut-il atténuer les risques de sécurité?" - }, - "mitigateDataRisks": { - "section": "Atténuer les risques liés aux données", - "description": "Comment le fournisseur d’API peut-il atténuer les risques liés aux données?" - }, "expectedBenefits": { "section": "Expected benefits", "description": "What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?" @@ -4413,8 +2940,8 @@ }, "customerJourneyCanvas": { "title": "Customer Journey Canvas", - "purpose": "Quel parcours client ou partenaire crée le besoin de capacité ou d’interface ?", - "howToUse": "Décrire un parcours réel de client, partenaire ou utilisateur, et non l’usage de l’API elle-même. Ce parcours révèle les irritants, objectifs et contextes qui aident à définir les exigences de capacité et d’interface.", + "purpose": "Quel parcours vit le client pertinent le plus externe, et que faut-il améliorer ?", + "howToUse": "Commencez par le client pertinent le plus externe. Décrivez son parcours réel avant de remonter vers les capacités, les processus internes ou les choix de mise en œuvre.", "sections": { "customerDiscoversNeed": { "section": "Le client découvre le besoin", @@ -4447,6 +2974,10 @@ "interactionProcessingRules": { "section": "Règles d'interaction et de traitement", "description": "Quelles sont les règles d'interaction et de traitement à chaque étape?" + }, + "improvementOpportunities": { + "section": "Opportunités d’amélioration", + "description": "Quelles étapes du parcours indiquent qu’une capacité ou un processus sous-jacent doit être créé, amélioré, automatisé ou supprimé ?" } } }, @@ -4782,887 +3313,424 @@ } }, "automationOpportunityCanvas": { - "title": "Canvas d’hypothèse d’automatisation", - "purpose": "Relie les preuves issues de canvases de support optionnels à une hypothèse d’automatisation testable avant de s’engager sur l’architecture ou la livraison.", - "howToUse": "Commencez par le Canvas d’hypothèse d’automatisation. Référencez le parcours, la proposition de valeur, le domaine, l’impact métier, la capacité ou d’autres preuves uniquement lorsqu’ils sont pertinents; ne répétez pas ces canvases ici.", + "title": "Automation Hypothesis & Validation Canvas", + "purpose": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "howToUse": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", "sections": { "hypothesis": { - "section": "Hypothesis", - "description": "What do we believe automating which work for which actor will achieve? Use the form: We believe automating [work] for [actor] will achieve [outcome]." + "section": "Automation hypothesis", + "description": "What work do we believe should be automated, and what outcome should it achieve?" }, - "supportingEvidence": { - "section": "Supporting evidence", - "description": "Which Journey, Value Proposition, Business Impact, Capacity, Domain, or other evidence supports this hypothesis? Link or reference existing artifacts instead of repeating them." - }, - "automationScope": { - "section": "Scope of automation", - "description": "Which part of the work is being considered for automation now, and what is explicitly outside scope?" - }, - "responsibilityAndSolutionHypothesis": { - "section": "Hypothèse initiale de mise en œuvre", - "description": "Quelle est l’hypothèse actuelle sur la façon dont l’automatisation pourrait être mise en œuvre? Il s’agit d’une hypothèse à valider, pas d’une décision d’architecture." + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the hypothesis?" }, "criticalAssumptions": { "section": "Critical assumptions", - "description": "Which assumptions could invalidate value, feasibility, safety, operability, compliance, or adoption?" + "description": "What could make the hypothesis wrong, unsafe, or unworkable?" }, "validationExperiment": { "section": "Validation experiment", - "description": "What is the smallest useful PoC or investigation, what evidence and thresholds decide success, and what stop conditions apply?" + "description": "What is the smallest useful test, evidence threshold, and stop condition?" }, "decision": { "section": "Decision", - "description": "What is the evidence-based decision: supported, revise and retest, redesign the process first, or reject?" + "description": "Proceed, revise, redesign the process, or stop?" } } }, - "humanAutomationResponsibilityCanvas": { - "title": "Human-Automation Responsibility Canvas", - "purpose": "Decide what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "howToUse": "List target process steps and decide the most appropriate performer for each step. Capture required oversight, escalation, and evidence so the solution does not assume every step should be automated.", + "automationWorkflowCanvas": { + "title": "Automation Workflow Canvas", + "purpose": "Concevoir le workflow interne nécessaire pour produire les résultats client et capacité sélectionnés.", + "howToUse": "Réutilisez les éléments du parcours client, de la proposition de valeur, du domaine et de la validation. Définissez le travail interne, répartissez-le entre humains et automatisation, puis ajoutez uniquement les détails d’exécution.", "sections": { - "processStep": { - "section": "Process step", - "description": "Which step in the target process is being assigned or reviewed?" + "selectedCustomerCapabilityOutcomes": { + "section": "Résultats client et capacité sélectionnés", + "description": "Quels résultats convenus pour le client et la capacité ce workflow doit-il produire ?" }, - "humanResponsibility": { - "section": "Human responsibility", - "description": "What should a person do, decide, approve, review, correct, or own?" + "internalWorkflowSteps": { + "section": "Étapes du workflow interne", + "description": "Quel travail interne doit être réalisé pour produire ces résultats ?" }, - "ruleOrWorkflowResponsibility": { - "section": "Rule or workflow responsibility", - "description": "What can be handled by deterministic rules, orchestration, routing, reminders, or scheduled workflow?" + "workAllocationHumanControl": { + "section": "Répartition du travail et contrôle humain", + "description": "Qu’est-ce qui reste humain, qu’est-ce qui est automatisé et où faut-il une supervision ou une escalade ?" }, - "agentOrAiResponsibility": { - "section": "Agent or AI responsibility", - "description": "What judgement, language, classification, generation, planning, or assistance may an agent or AI perform?" + "inputsOutputsInteractions": { + "section": "Entrées, sorties et interactions", + "description": "Quelles informations, quels systèmes et quels transferts sont nécessaires ?" }, - "apiOrSystemResponsibility": { - "section": "API or system responsibility", - "description": "What should be performed through system capability, API, event, connector, file, or direct integration?" + "decisionsExceptionsRecovery": { + "section": "Décisions, exceptions et reprise", + "description": "Qu’est-ce qui modifie le flux, qu’est-ce qui peut échouer et comment le travail est-il repris ?" }, - "rpaOrUiAutomationResponsibility": { - "section": "RPA or UI automation responsibility", - "description": "Where is UI automation justified because no suitable system, API, event, connector, or data access path exists?" - }, - "requiredOversight": { - "section": "Required oversight", - "description": "What human supervision, approval, confirmation, monitoring, or review is required before or after the step?" - }, - "escalation": { - "section": "Escalation", - "description": "When should the step stop, ask for help, route to a person, or move to another support path?" - }, - "evidenceOrAuditTrail": { - "section": "Evidence or audit trail", - "description": "What record proves what happened, who or what acted, what data was used, and what decision was made?" + "evidenceMonitoring": { + "section": "Preuves et suivi", + "description": "Qu’est-ce qui prouve le bon fonctionnement et montre si le résultat attendu a été atteint ?" } } }, - "automationWorkflowCanvas": { - "title": "Canvas de workflow d’automatisation", - "purpose": "Concevoir la séquence, les états, les données, les déclencheurs, les décisions, les interactions, les chemins d’échec et la récupération du workflow d’automatisation de bout en bout.", - "howToUse": "Utilisez l’allocation des responsabilités du Canvas de responsabilité humain-automatisation comme entrée. Concentrez-vous ici sur la façon dont le workflow s’exécute, change d’état, échange des données, gère les exceptions, produit des preuves et récupère.", + "automationArchitectureDecisionCanvas": { + "title": "Automation Architecture Decision Canvas", + "purpose": "Choose the implementation approach using evidence already gathered.", + "howToUse": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", "sections": { - "trigger": { - "section": "Trigger", - "description": "What event, schedule, user action, message, data change, or manual request starts the automation?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which requirements, capacity, location, impact, and responsibility decisions constrain the choice?" }, - "inputs": { - "section": "Inputs", - "description": "What data, documents, messages, forms, records, or context are required at the start and during the workflow?" + "viableOptions": { + "section": "Viable options", + "description": "Which human, workflow, rule, agent, API, connector, custom, or UI automation options remain viable?" }, - "workflowStages": { - "section": "Workflow stages and states", - "description": "What are the main workflow stages and states from trigger to completion, including waiting, review, exception, and completion states?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style or hybrid is selected?" }, - "decisionsAndRules": { - "section": "Decisions and rules", - "description": "Which deterministic rules, validations, thresholds, policies, or decision points shape the flow?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "agentActions": { - "section": "Automation actions", - "description": "What may the automation, workflow, rule, agent, integration, API, RPA, or system component do at each relevant stage?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "systemInteractions": { - "section": "System interactions", - "description": "Which systems, APIs, events, connectors, custom components, files, or screens are called or updated?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" + } + } + }, + "automationReadinessOperationsCanvas": { + "title": "Automation Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before readiness review.", + "howToUse": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", + "sections": { + "ownership": { + "section": "Ownership", + "description": "Who owns business outcomes, operations, support, and changes?" }, - "dataSources": { - "section": "Data sources", - "description": "Which source systems, datasets, records, documents, or knowledge sources are used and trusted?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, permissions, credentials, and identities ready?" }, - "humanTasks": { - "section": "Human checkpoints", - "description": "Where does the responsibility allocation require approval, confirmation, judgement, correction, review, or manual completion?" + "testEvidence": { + "section": "Test evidence", + "description": "What proves correct, safe, and reliable behavior?" }, - "handoffs": { - "section": "Handoffs and queues", - "description": "Where does work move between automation components, people, support teams, systems, queues, or exception paths?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, incidents, users, and operators be supported?" }, - "exceptions": { - "section": "Exceptions", - "description": "What error, missing-data, conflicting-data, timeout, permission, unsafe-action, or business exception scenarios must be handled?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will exceptions, fallback, rollback, and manual recovery work?" }, - "retriesAndTimeouts": { - "section": "Retries and timeouts", - "description": "Where are retries, timeout limits, duplicate prevention, idempotency, pause rules, or compensation required?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are documentation, risks, conditions, and blocking gaps clear?" + } + } + }, + "integrationCapabilityHypothesisCanvas": { + "title": "Integration Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable integration capability should proceed.", + "howToUse": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", + "sections": { + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed integration capability and reuse scope are being tested?" }, - "outputs": { - "section": "Outputs", - "description": "What records, decisions, messages, documents, updates, notifications, or outcomes are produced?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, - "auditEvidence": { - "section": "Audit evidence", - "description": "What log, trace, approval, run history, input snapshot, output record, or explanation proves correct operation?" + "criticalAssumptions": { + "section": "Critical assumptions", + "description": "What could invalidate value, reuse, ownership, feasibility, or adoption?" }, - "monitoringPoints": { - "section": "Monitoring points", - "description": "Which run, failure, exception, latency, cost, intervention, quality, safety, or outcome metrics should be observed?" + "validationStep": { + "section": "Validation step", + "description": "What is the smallest useful validation and success threshold?" }, - "recoveryPath": { - "section": "Recovery path", - "description": "How can the process be paused, rolled back, compensated, rerun, corrected, or completed manually?" + "decision": { + "section": "Decision", + "description": "Proceed, narrow, revise and retest, or stop?" } } }, - "automationArchitectureDecisionCanvas": { - "title": "Canvas de décision d’architecture d’automatisation", - "purpose": "Comparer et justifier les mécanismes de mise en œuvre alternatifs pour une solution d’automatisation.", - "howToUse": "Marquez chaque mécanisme candidat comme examiné, sélectionné, rejeté ou non pertinent. Comparez uniquement les candidats viables, individuellement et en combinaison hybride, puis justifiez l’approche recommandée selon la faisabilité, la fiabilité, la sécurité, la maintenabilité, la latence, la scalabilité, le coût, les dépendances, la testabilité, l’observabilité, la récupérabilité, les compétences et l’adéquation architecturale.", + "integrationConsumerProviderRequirementsCanvas": { + "title": "Integration Consumer & Provider Commitments Canvas", + "purpose": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "howToUse": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", "sections": { - "nativeFeature": { - "section": "Native feature", - "description": "Can an existing system capability solve this step with acceptable reliability, controls, and ownership?" + "selectedPartiesAndUseCases": { + "section": "Selected parties and use cases", + "description": "Which producers, providers, consumers, and use cases are covered?" }, - "workflow": { - "section": "Workflow", - "description": "Where is workflow orchestration, scheduling, routing, approval, notification, or coordination the best fit?" + "providerCommitments": { + "section": "Provider commitments", + "description": "What will providers deliver, maintain, monitor, and support?" }, - "rule": { - "section": "Rule", - "description": "Which decisions can be implemented as deterministic business rules, policy checks, validations, or calculations?" + "consumerCommitments": { + "section": "Consumer commitments", + "description": "What must consumers test, protect, operate, and communicate?" }, - "agent": { - "section": "Agent", - "description": "Where could an agent or AI safely add judgement, language understanding, generation, planning, or assistance?" + "accessAndValidationAgreement": { + "section": "Access and validation", + "description": "How will access, environments, credentials, and conformance be handled?" }, - "connector": { - "section": "Connector", - "description": "Which low-code, platform, SaaS, file, message, or data connectors are viable?" + "failureAndRecoveryAgreement": { + "section": "Failure and recovery", + "description": "Who handles failures, replay, duplicates, reconciliation, and recovery?" }, - "api": { - "section": "API", - "description": "Where is an API call the best fit for reliable, governed, testable system interaction?" + "changeAndLifecycleAgreement": { + "section": "Change and lifecycle", + "description": "How will compatibility, migration, notice, deprecation, and retirement work?" + } + } + }, + "integrationArchitectureDecisionCanvas": { + "title": "Integration Architecture Decision Canvas", + "purpose": "Choose the integration style and platform using evidence already gathered.", + "howToUse": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", + "sections": { + "reusedInputs": { + "section": "Reused inputs", + "description": "Which commitments, capacity, location, impact, and domain decisions constrain the choice?" }, - "event": { - "section": "Event", - "description": "Where should the solution react to, publish, or consume events?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, messaging, file, stream, data, connector, platform, or custom options remain viable?" }, - "customCode": { - "section": "Custom code", - "description": "Where is custom code justified because standard capabilities are insufficient or too risky?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which integration style, platform, or hybrid is selected?" }, - "rpa": { - "section": "RPA", - "description": "Where is desktop or UI automation justified, and what fragility or recovery controls are required?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "humanTask": { - "section": "Human task", - "description": "Which steps should remain human because of judgement, accountability, risk, consent, policy, or exception handling?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "feasibilityReliabilitySecurity": { - "section": "Feasibility, reliability, security", - "description": "How do candidates compare on technical feasibility, expected reliability, identity, authorization, data exposure, and control strength?" - }, - "maintainabilityScalabilityCost": { - "section": "Maintainability, scalability, cost", - "description": "How do candidates compare on change effort, operating cost, licence cost, transaction volume, peak load, and lifecycle maintenance?" - }, - "latencyObservabilityRecoverability": { - "section": "Latency, observability, recoverability", - "description": "How do candidates compare on timing needs, monitoring, logs, traceability, retry, compensation, and manual recovery?" - }, - "skillsVendorFit": { - "section": "Skills, vendor dependency, architectural fit", - "description": "What skills, ownership, platform dependencies, governance constraints, and architecture standards affect the decision?" - }, - "recommendedHybridApproach": { - "section": "Recommended hybrid approach", - "description": "Which combination of people, rules, workflows, agents, systems, APIs, events, custom code, and UI automation should be used?" - }, - "decisionRationale": { - "section": "Decision rationale", - "description": "Why is this approach preferred over the alternatives, and what evidence supports the decision?" - }, - "openQuestionsAndRisks": { - "section": "Open questions and risks", - "description": "Which assumptions, risks, dependencies, or unresolved constraints must be validated before delivery or release?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, - "automationReadinessOperationsCanvas": { - "title": "Canvas de préparation et d’exploitation de l’automatisation", - "purpose": "Préparer le modèle opérationnel pour une automatisation pouvant être publiée, supportée, surveillée et récupérée en sécurité.", - "howToUse": "Use this during delivery to prepare ownership, environments, access, evidence, monitoring, support, fallback, rollback, runbooks, known risks, and the deployment decision. Use the readiness checklist later for the release gate.", + "integrationReadinessOperationsCanvas": { + "title": "Integration Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before integration readiness review.", + "howToUse": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Who accepts business value, process impact, residual risk, and release timing?" + "ownership": { + "section": "Ownership", + "description": "Who owns business, integration, producer, consumer, platform, and incident responsibilities?" }, - "operationalOwner": { - "section": "Operational owner", - "description": "Who owns runtime supervision, incidents, support, runbooks, changes, and recovery?" - }, - "users": { - "section": "Users", - "description": "Which users, operators, approvers, support teams, or process participants are affected?" - }, - "permissions": { - "section": "Permissions", - "description": "What human, service, system, data, role, and approval permissions are required and approved?" - }, - "credentials": { - "section": "Credentials", - "description": "How are credentials, secrets, certificates, tokens, delegated access, and service identities managed?" - }, - "environments": { - "section": "Environments", - "description": "Which development, test, staging, production, desktop, cloud, or platform environments are used?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, credentials, connectivity, permissions, and sequencing ready?" }, "testEvidence": { "section": "Test evidence", - "description": "What proves functional correctness, rule behavior, integration behavior, agent behavior, permissions, performance, and exceptions?" - }, - "exceptionHandling": { - "section": "Exception handling", - "description": "How are errors, missing data, unsafe actions, failed runs, retries, timeouts, and handoffs handled?" - }, - "monitoring": { - "section": "Monitoring", - "description": "Which run, failure, exception, latency, cost, intervention, value, safety, and outcome signals are monitored?" - }, - "support": { - "section": "Support", - "description": "Who supports users and operators, how are incidents raised, and what service expectations apply?" - }, - "manualFallback": { - "section": "Manual fallback", - "description": "How can work continue manually if the automation is paused, unavailable, incorrect, or unsafe?" - }, - "rollback": { - "section": "Rollback", - "description": "How can changes, actions, data updates, releases, or workflow versions be reversed or compensated?" - }, - "documentation": { - "section": "Documentation", - "description": "What operating instructions, design records, architecture decisions, user guidance, and runbooks are ready?" - }, - "deploymentDecision": { - "section": "Statut de préparation à la publication", - "description": "Qu’est-ce qui reste incomplet, conditionnel ou bloquant avant la décision formelle de préparation?" - }, - "knownRisks": { - "section": "Known risks", - "description": "Which risks are accepted, mitigated, deferred, or blocking release?" - }, - "improvementBacklog": { - "section": "Improvement backlog", - "description": "Which improvements, unresolved assumptions, PoC findings, and future enhancements should be prioritized next?" - } - } - }, - "integrationCapabilityHypothesisCanvas": { - "title": "Canvas d’hypothèse de capacité d’intégration", - "purpose": "Prioriser une hypothèse de capacité d’intégration réutilisable en reliant les preuves consommateurs, valeur, domaine, propriété, réutilisation et viabilité à un périmètre clair, des hypothèses, une validation et une décision poursuivre ou arrêter.", - "howToUse": "Commencez ici avant le choix d’architecture. Référencez les preuves de parcours, proposition de valeur, domaine, modèle métier, impact, capacité ou autres uniquement lorsqu’elles soutiennent l’hypothèse.", - "sections": { - "hypothesis": { - "section": "Hypothèse de capacité d’intégration", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Hypothèse de capacité d’intégration?" - }, - "consumersAndReuseScope": { - "section": "Consommateurs visés et périmètre de réutilisation", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Consommateurs visés et périmètre de réutilisation?" - }, - "providerAndOwner": { - "section": "Fournisseur et propriétaire", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Fournisseur et propriétaire?" - }, - "supportingEvidence": { - "section": "Preuves de support", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Preuves de support?" - }, - "implementationStyleHypothesis": { - "section": "Hypothèse initiale de style d’implémentation", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Hypothèse initiale de style d’implémentation?" - }, - "criticalAssumptions": { - "section": "Hypothèses critiques", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Hypothèses critiques?" - }, - "validationExperiment": { - "section": "Expérience de validation", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Expérience de validation?" - }, - "decision": { - "section": "Décision", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Décision?" - } - } - }, - "integrationConsumerProviderRequirementsCanvas": { - "title": "Canvas des exigences consommateur et fournisseur d’intégration", - "purpose": "Capturer les besoins des systèmes consommateurs, équipes, producteurs, fournisseurs et opérateurs avant de choisir ou concevoir l’implémentation d’intégration.", - "howToUse": "Utilisez ceci pour rendre explicites onboarding, accès, environnements, identité, compatibilité, attentes de service, qualité des données, support et exigences de récupération.", - "sections": { - "consumerSystemsAndTeams": { - "section": "Systèmes consommateurs et équipes", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Systèmes consommateurs et équipes?" - }, - "providerResponsibilities": { - "section": "Responsabilités du fournisseur", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Responsabilités du fournisseur?" - }, - "interactionAndDataNeeds": { - "section": "Besoins d’interaction et de données", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Besoins d’interaction et de données?" - }, - "onboardingAndAccess": { - "section": "Onboarding et accès", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Onboarding et accès?" - }, - "environmentsAndTestAccess": { - "section": "Environnements et accès de test", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Environnements et accès de test?" - }, - "credentialsAndIdentity": { - "section": "Identifiants et identité", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Identifiants et identité?" - }, - "compatibilityAndVersioning": { - "section": "Compatibilité et versioning", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Compatibilité et versioning?" - }, - "serviceExpectations": { - "section": "Attentes de service", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Attentes de service?" - }, - "dataQualityAndObservability": { - "section": "Qualité des données et observabilité", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Qualité des données et observabilité?" - }, - "supportAndFailureHandling": { - "section": "Support et gestion des échecs", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Support et gestion des échecs?" - }, - "replayReconciliationRecovery": { - "section": "Replay, réconciliation, récupération", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Replay, réconciliation, récupération?" - } - } - }, - "integrationArchitectureDecisionCanvas": { - "title": "Canvas de décision d’architecture d’intégration", - "purpose": "Comparer et justifier les styles d’implémentation d’intégration, les capacités plateforme, les contraintes de gouvernance et les alternatives rejetées.", - "howToUse": "Utilisez le contrôle de statut partagé pour marquer chaque style candidat comme considéré, sélectionné, rejeté ou non pertinent. Comparez les options viables selon temporalité, couplage, propriété des données, cohérence, fiabilité, sécurité, maintenabilité, observabilité, récupération, coût, gouvernance et compétences.", - "sections": { - "synchronousApi": { - "section": "API synchrone", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour API synchrone?" - }, - "eventDriven": { - "section": "Événement asynchrone", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Événement asynchrone?" - }, - "messagingQueue": { - "section": "Messagerie ou file", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Messagerie ou file?" - }, - "batchFileExchange": { - "section": "Échange batch ou fichier", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Échange batch ou fichier?" - }, - "stream": { - "section": "Stream", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Stream?" - }, - "etlElt": { - "section": "ETL ou ELT", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour ETL ou ELT?" - }, - "dataProduct": { - "section": "Produit de données", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Produit de données?" - }, - "directDatabase": { - "section": "Intégration directe base de données", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Intégration directe base de données?" - }, - "sharedPlatform": { - "section": "Plateforme d’intégration partagée", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Plateforme d’intégration partagée?" - }, - "pointToPoint": { - "section": "Point-à-point", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Point-à-point?" - }, - "managedConnector": { - "section": "Connecteur managé", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Connecteur managé?" - }, - "customIntegration": { - "section": "Intégration spécifique", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Intégration spécifique?" - }, - "hybridApproach": { - "section": "Approche hybride", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Approche hybride?" - }, - "evaluationCriteria": { - "section": "Critères d’évaluation", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Critères d’évaluation?" - }, - "selectedStyleAndPlatform": { - "section": "Style et plateforme sélectionnés", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Style et plateforme sélectionnés?" - }, - "rationaleAndRejectedAlternatives": { - "section": "Justification et alternatives rejetées", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Justification et alternatives rejetées?" - }, - "openRisksAndAssumptions": { - "section": "Risques et hypothèses ouverts", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Risques et hypothèses ouverts?" - } - } - }, - "integrationReadinessOperationsCanvas": { - "title": "Canvas de préparation et d’exploitation de l’intégration", - "purpose": "Préparer le modèle opérationnel d’une capacité d’intégration réutilisable pouvant être publiée, supportée, surveillée et récupérée en sécurité.", - "howToUse": "Utilisez ceci pendant la livraison pour préparer propriété, environnements, identifiants, déploiement, monitoring, support, retry, replay, réconciliation, fallback, rollback, incidents, preuves de test, risques et statut de préparation.", - "sections": { - "businessOwner": { - "section": "Propriétaire métier", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Propriétaire métier?" + "description": "What proves contract, mapping, compatibility, quality, resilience, and recovery?" }, - "integrationOwner": { - "section": "Propriétaire de l’intégration", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Propriétaire de l’intégration?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will producers, consumers, platforms, incidents, and service questions be supported?" }, - "producerOwners": { - "section": "Propriétaires producteurs", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Propriétaires producteurs?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will retry, replay, duplicates, reconciliation, fallback, and compensation work?" }, - "consumerOwners": { - "section": "Propriétaires consommateurs", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Propriétaires consommateurs?" - }, - "platformOwner": { - "section": "Propriétaire plateforme", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Propriétaire plateforme?" - }, - "environments": { - "section": "Environnements", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Environnements?" - }, - "credentials": { - "section": "Identifiants", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Identifiants?" - }, - "deployment": { - "section": "Déploiement", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Déploiement?" - }, - "monitoring": { - "section": "Monitoring", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Monitoring?" - }, - "support": { - "section": "Support", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Support?" - }, - "retryReplay": { - "section": "Retry et replay", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Retry et replay?" - }, - "reconciliation": { - "section": "Réconciliation", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Réconciliation?" - }, - "fallbackRollback": { - "section": "Fallback et rollback", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Fallback et rollback?" - }, - "incidentOwnership": { - "section": "Responsabilité incidents", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Responsabilité incidents?" - }, - "testEvidenceKnownRisks": { - "section": "Preuves de test et risques connus", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Preuves de test et risques connus?" - }, - "readinessStatus": { - "section": "Statut de préparation", - "description": "Quelles informations, preuves, décisions et questions ouvertes doivent être consignées pour Statut de préparation?" - }, - "documentationDependenciesChangeReadiness": { - "section": "Documentation, dépendances et préparation au changement", - "description": "Les contrats, mappings, runbooks, dépendances, instructions de migration, séquence de déploiement, cutover, compatibilité ascendante, propriété des versions et responsabilités de changement sont-ils prêts?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are contracts, runbooks, dependencies, risks, conditions, and blocking gaps clear?" } } }, "integrationSolutionDesignCanvas": { - "title": "Canvas de conception de solution d’intégration", - "purpose": "Résume la conception complète de l’intégration tous styles d’implémentation confondus, y compris contrats, schémas, structures de données, mappings, comportement de livraison, sécurité, erreurs, observabilité, réconciliation et versioning.", - "howToUse": "Utilisez ceci comme artefact principal de conception après la décision d’architecture. Utilisez Interaction Canvas, REST, Event, GraphQL, fichier, stream, produit de données ou messagerie comme support détaillé conditionnel.", + "title": "Integration Solution Design Canvas", + "purpose": "Refine the selected architecture into an implementable integration design.", + "howToUse": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", "sections": { - "selectedIntegrationStyle": { - "section": "Style d’intégration sélectionné", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Style d’intégration sélectionné?" - }, - "producerAndConsumer": { - "section": "Producteur et consommateur", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Producteur et consommateur?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which architecture, domain, interaction, and commitment decisions are reused?" }, - "contractAndSchema": { - "section": "Contrat et schéma", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Contrat et schéma?" + "contractAndModel": { + "section": "Contract and model", + "description": "What contract, schema, data model, and version define the integration?" }, - "mappingsAndTransformations": { - "section": "Mappings et transformations", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Mappings et transformations?" + "mappingAndDelivery": { + "section": "Mapping and delivery", + "description": "What transformations, delivery pattern, and metadata are required?" }, - "interactionDeliveryPattern": { - "section": "Modèle d’interaction ou de livraison", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Modèle d’interaction ou de livraison?" + "errorsAndRecovery": { + "section": "Errors and recovery", + "description": "How are failures, retries, replay, duplicates, and reconciliation handled?" }, - "identityAndSecurity": { - "section": "Identité et sécurité", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Identité et sécurité?" - }, - "errorRetryReplay": { - "section": "Modèle d’erreur, retry, replay", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Modèle d’erreur, retry, replay?" - }, - "correlationMetadata": { - "section": "Corrélation et métadonnées", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Corrélation et métadonnées?" - }, - "reconciliationRules": { - "section": "Règles de réconciliation", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Règles de réconciliation?" - }, - "observability": { - "section": "Observabilité", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Observabilité?" + "securityAndTrust": { + "section": "Security and trust", + "description": "What identity, access, privacy, and trust controls apply?" }, - "versioningEvolution": { - "section": "Versioning et évolution", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Versioning et évolution?" - }, - "canonicalConsumerSpecificModel": { - "section": "Modèle canonique vs spécifique consommateur", - "description": "Quelles décisions de conception, règles, preuves et questions ouvertes doivent être consignées pour Modèle canonique vs spécifique consommateur?" + "observabilityAndEvolution": { + "section": "Observability and evolution", + "description": "How will the integration be monitored, changed, migrated, and deprecated?" } } }, "capabilityHypothesisCanvas": { - "title": "Canvas d’hypothèse de capacité", - "purpose": "Prioriser une hypothèse de capacité numérique réutilisable en reliant les preuves consommateur, valeur, domaine, propriété, viabilité et réutilisation à un périmètre clair, des hypothèses, une validation et une décision.", - "howToUse": "Quelles décisions, preuves et questions ouvertes doivent être consignées pour Canvas d’hypothèse de capacité?", + "title": "Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable digital capability should proceed.", + "howToUse": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", "sections": { - "hypothesis": { - "section": "Hypothèse de capacité", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Hypothèse de capacité?" - }, - "targetConsumersUseCases": { - "section": "Consommateurs cibles et cas d’usage", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Consommateurs cibles et cas d’usage?" - }, - "reusableScope": { - "section": "Périmètre réutilisable prévu", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Périmètre réutilisable prévu?" - }, - "supportingEvidence": { - "section": "Preuves de support", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Preuves de support?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed capability and reusable scope are being tested?" }, - "expectedOutcomes": { - "section": "Résultats attendus", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Résultats attendus?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { - "section": "Hypothèses critiques", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Hypothèses critiques?" + "section": "Critical assumptions", + "description": "What could invalidate value, reuse, ownership, sustainability, or adoption?" }, "minimumValidation": { - "section": "Validation minimale", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Validation minimale?" + "section": "Minimum validation", + "description": "What is the smallest useful validation and success threshold?" }, "decision": { - "section": "Décision", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Décision?" + "section": "Decision", + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "capabilityConsumerProducerRequirementsCanvas": { - "title": "Canvas des exigences consommateur et producteur", - "purpose": "Capturer ce dont consommateurs, producteurs, propriétaires, opérateurs et équipes support ont besoin d’une capacité réutilisable avant de choisir ou concevoir le style d’implémentation.", - "howToUse": "Quelles décisions, preuves et questions ouvertes doivent être consignées pour Canvas des exigences consommateur et producteur?", + "title": "Capability Consumer & Producer Commitments Canvas", + "purpose": "Agree mutual commitments for providing and consuming a reusable capability.", + "howToUse": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", "sections": { - "intendedConsumersContexts": { - "section": "Consommateurs et contextes prévus", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Consommateurs et contextes prévus?" - }, - "capabilityOwnerProducerResponsibilities": { - "section": "Propriétaire de capacité et responsabilités producteur", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Propriétaire de capacité et responsabilités producteur?" - }, - "discoveryEvaluation": { - "section": "Découverte et évaluation", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Découverte et évaluation?" + "selectedConsumersAndUseCases": { + "section": "Selected consumers and use cases", + "description": "Which consumers and usage contexts are covered?" }, - "accessOnboarding": { - "section": "Accès et onboarding", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Accès et onboarding?" + "ownerAndProducerCommitments": { + "section": "Owner and producer commitments", + "description": "What will owners and producers provide, maintain, monitor, and support?" }, - "serviceExpectations": { - "section": "Attentes de service", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Attentes de service?" - }, - "qualityAvailability": { - "section": "Attentes de qualité et disponibilité", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Attentes de qualité et disponibilité?" - }, - "changeLifecycle": { - "section": "Attentes de changement et cycle de vie", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Attentes de changement et cycle de vie?" - }, - "supportIncidentCommunication": { - "section": "Support et communication incident", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Support et communication incident?" - }, - "operationalGovernanceConstraints": { - "section": "Contraintes opérationnelles et gouvernance", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Contraintes opérationnelles et gouvernance?" + "consumerResponsibilities": { + "section": "Consumer responsibilities", + "description": "What must consumers do for appropriate use, access, testing, and feedback?" }, - "producerCommitments": { - "section": "Engagements producteur", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Engagements producteur?" + "accessAndOnboardingAgreement": { + "section": "Access and onboarding", + "description": "What discovery, approval, testing, and onboarding path is agreed?" }, - "consumerResponsibilities": { - "section": "Responsabilités consommateur", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Responsabilités consommateur?" + "serviceAndLifecycleAgreement": { + "section": "Service and lifecycle", + "description": "What service, change, deprecation, and retirement commitments are agreed?" }, - "architectureImplications": { - "section": "Implications d’architecture", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Implications d’architecture?" + "openCommitments": { + "section": "Open commitments", + "description": "What remains unresolved before architecture or delivery?" } } }, "capabilityArchitectureDecisionCanvas": { - "title": "Canvas de décision d’architecture de capacité", - "purpose": "Comparer les options d’implémentation et enregistrer le style d’implémentation de capacité sélectionné, la plateforme, la justification, les alternatives rejetées, les hypothèses et les risques.", - "howToUse": "Utilisez le contrôle de statut partagé pour marquer chaque style candidat comme considéré, sélectionné, rejeté ou non pertinent. Comparez les options selon besoins consommateurs, réutilisation, couplage, latence, temporalité, volume, propriété des données, cohérence, sécurité, frontières de confiance et localisation, fiabilité, opérabilité, coût, compétences, adéquation plateforme, gouvernance, découvrabilité et gestion du cycle de vie.", + "title": "Capability Architecture Decision Canvas", + "purpose": "Choose how the capability will be delivered using evidence already gathered.", + "howToUse": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", "sections": { - "api": { - "section": "API", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour API?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which earlier decisions and constraints shape the implementation choice?" }, - "event": { - "section": "Événement", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Événement?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, workflow, application, data product, shared service, human service, or hybrid options remain viable?" }, - "fileBatch": { - "section": "Fichier ou batch", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Fichier ou batch?" - }, - "stream": { - "section": "Stream", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Stream?" - }, - "dataProduct": { - "section": "Produit de données", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Produit de données?" - }, - "workflow": { - "section": "Workflow", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Workflow?" - }, - "sharedService": { - "section": "Service partagé", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Service partagé?" - }, - "userFacingApplication": { - "section": "Application utilisateur", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Application utilisateur?" - }, - "directIntegration": { - "section": "Intégration directe", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Intégration directe?" - }, - "platformNativeFeature": { - "section": "Fonction native plateforme", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Fonction native plateforme?" - }, - "humanAssistedService": { - "section": "Service assisté par humain", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Service assisté par humain?" - }, - "hybridApproach": { - "section": "Approche hybride", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Approche hybride?" - }, - "evaluationCriteria": { - "section": "Critères d’évaluation", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Critères d’évaluation?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style and enabling platform are selected?" }, - "selectedStylePlatform": { - "section": "Style et plateforme sélectionnés", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Style et plateforme sélectionnés?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "rationaleRejectedAlternatives": { - "section": "Justification et alternatives rejetées", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Justification et alternatives rejetées?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "assumptionsRisks": { - "section": "Hypothèses et risques", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Hypothèses et risques?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "capabilitySolutionDesignCanvas": { - "title": "Canvas de conception de solution de capacité", - "purpose": "Concevoir comment les consommateurs accèdent, interagissent, reçoivent ou utilisent la capacité via le style d’implémentation sélectionné.", - "howToUse": "Quelles décisions, preuves et questions ouvertes doivent être consignées pour Canvas de conception de solution de capacité?", + "title": "Capability Solution Design Canvas", + "purpose": "Refine the selected implementation style into a clear consumer-facing capability design.", + "howToUse": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", "sections": { - "selectedImplementationStyle": { - "section": "Style d’implémentation sélectionné", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Style d’implémentation sélectionné?" - }, - "serviceBoundary": { - "section": "Frontière de service", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Frontière de service?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which earlier journey, value, domain, commitment, and architecture decisions are reused?" }, - "consumerInteractionModel": { - "section": "Modèle d’interaction consommateur", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Modèle d’interaction consommateur?" - }, - "dataBusinessConcepts": { - "section": "Concepts données et métier", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Concepts données et métier?" - }, - "contractOrServiceDefinition": { - "section": "Contrat ou définition de service", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Contrat ou définition de service?" - }, - "responsibilitiesRules": { - "section": "Responsabilités et règles", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Responsabilités et règles?" - }, - "inputsOutputs": { - "section": "Entrées et sorties", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Entrées et sorties?" + "boundaryAndInteraction": { + "section": "Boundary and interaction", + "description": "What belongs inside the capability, and how do consumers use it?" }, - "errorsExceptions": { - "section": "Erreurs et exceptions", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Erreurs et exceptions?" + "contractRulesAndOutcomes": { + "section": "Contract, rules, and outcomes", + "description": "What behavior, responsibilities, inputs, outputs, and outcomes are promised?" }, - "lifecycleVersioning": { - "section": "Cycle de vie et versioning", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Cycle de vie et versioning?" + "errorsAndSecurity": { + "section": "Errors and security", + "description": "How are exceptions, access, privacy, and trust handled?" }, - "securityPrivacy": { - "section": "Sécurité et confidentialité", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Sécurité et confidentialité?" + "lifecycleAndSupport": { + "section": "Lifecycle and support", + "description": "How will change, versioning, support, deprecation, and retirement work?" }, "observability": { - "section": "Observabilité", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Observabilité?" - }, - "supportModel": { - "section": "Modèle de support", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Modèle de support?" + "section": "Observability", + "description": "What health, usage, quality, value, and consumer signals must be visible?" } } }, "capabilityReadinessOperationsCanvas": { - "title": "Canvas de préparation et d’exploitation de capacité", - "purpose": "Préparer le modèle opérationnel d’une capacité réutilisable avant la décision formelle de préparation.", - "howToUse": "Quelles décisions, preuves et questions ouvertes doivent être consignées pour Canvas de préparation et d’exploitation de capacité?", + "title": "Capability Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before capability readiness review.", + "howToUse": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", "sections": { - "businessOwner": { - "section": "Propriétaire métier", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Propriétaire métier?" - }, - "capabilityOwner": { - "section": "Propriétaire de capacité", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Propriétaire de capacité?" - }, - "producerOwner": { - "section": "Propriétaire producteur", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Propriétaire producteur?" - }, - "operationalOwner": { - "section": "Propriétaire opérationnel", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Propriétaire opérationnel?" - }, - "consumers": { - "section": "Consommateurs", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Consommateurs?" - }, - "implementationStyle": { - "section": "Style d’implémentation", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Style d’implémentation?" - }, - "environments": { - "section": "Environnements", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Environnements?" + "ownership": { + "section": "Ownership", + "description": "Who owns value, the capability lifecycle, production, operations, support, and changes?" }, - "permissionsCredentials": { - "section": "Permissions et identifiants", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Permissions et identifiants?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are required environments, access, permissions, and credentials ready?" }, "testEvidence": { - "section": "Preuves de test", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Preuves de test?" - }, - "serviceExpectations": { - "section": "Attentes de service", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Attentes de service?" - }, - "monitoring": { - "section": "Monitoring", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Monitoring?" - }, - "support": { - "section": "Support", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Support?" - }, - "fallbackContinuity": { - "section": "Fallback et continuité", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Fallback et continuité?" - }, - "changeOwnership": { - "section": "Responsabilité du changement", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Responsabilité du changement?" - }, - "documentationRunbooks": { - "section": "Documentation et runbooks", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Documentation et runbooks?" + "section": "Test evidence", + "description": "What proves outcomes, quality, security, compatibility, resilience, and consumer usability?" }, - "readinessStatus": { - "section": "Statut de préparation", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Statut de préparation?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, usage, value, incidents, consumers, and operators be supported?" }, - "knownRisks": { - "section": "Risques connus", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Risques connus?" + "failureAndRecovery": { + "section": "Continuity and recovery", + "description": "How will service continue, degrade safely, recover, or fall back?" }, - "improvementBacklog": { - "section": "Backlog d’amélioration", - "description": "Quelles décisions concrètes, preuves, responsabilités, risques et prochaines étapes doivent être consignés pour Backlog d’amélioration?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are service definitions, runbooks, risks, conditions, and blocking gaps clear?" } } } @@ -5739,30 +3807,6 @@ "purpose": "Que valor, risco e impactos operacionais, financeiros, de clientes, colaboradores, conformidade e estratégicos são esperados ou estão em causa?", "howToUse": "Use this to connect expected benefits and consequences to architecture, prioritization, readiness, and proceed-or-stop decisions. Include the impact of not proceeding as well as critical risks and mitigations.", "sections": { - "availabilityRisks": { - "section": "Riscos de disponibilidade", - "description": "Quais são os riscos potenciais para a disponibilidade da API?" - }, - "securityRisks": { - "section": "Riscos de segurança", - "description": "Quais são os riscos potenciais de segurança associados à API?" - }, - "dataRisks": { - "section": "Riscos de dados", - "description": "Quais são os riscos potenciais para a integridade ou confidencialidade dos dados?" - }, - "mitigateAvailabilityRisks": { - "section": "Mitigar riscos de disponibilidade", - "description": "Como o fornecedor da API pode mitigar os riscos de disponibilidade?" - }, - "mitigateSecurityRisks": { - "section": "Mitigar riscos de segurança", - "description": "Como o fornecedor da API pode mitigar os riscos de segurança?" - }, - "mitigateDataRisks": { - "section": "Mitigar riscos de dados", - "description": "Como o fornecedor da API pode mitigar os riscos de dados?" - }, "expectedBenefits": { "section": "Expected benefits", "description": "What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?" @@ -5830,8 +3874,8 @@ }, "customerJourneyCanvas": { "title": "Canvas do Percurso do Cliente", - "purpose": "Qual é a percurso do cliente ou parceiro que a API pretende apoiar?", - "howToUse": "Descreva uma percurso real de um cliente ou utilizador — não o uso da API — para revelar pontos fracos, objetivos e contexto. Esta informação ajuda a definir que tipo de apoio de API será realmente necessário mais tarde.", + "purpose": "Que jornada vive o cliente relevante mais externo e o que deve ser melhorado?", + "howToUse": "Comece pelo cliente relevante mais externo. Descreva primeiro a jornada real antes de avançar para capacidades, processos internos ou decisões de implementação.", "sections": { "customerDiscoversNeed": { "section": "O cliente descobre a necessidade", @@ -5864,6 +3908,10 @@ "interactionProcessingRules": { "section": "Regras de interação e processamento", "description": "Quais são as regras de interação e processamento em cada etapa?" + }, + "improvementOpportunities": { + "section": "Oportunidades de melhoria", + "description": "Que etapas da jornada indicam que uma capacidade ou processo subjacente deve ser criado, melhorado, automatizado ou removido?" } } }, @@ -6199,887 +4247,424 @@ } }, "automationOpportunityCanvas": { - "title": "Canvas de Hipótese de Automação", - "purpose": "Liga evidências de canvases de apoio opcionais a uma hipótese de automação testável antes de avançar para arquitetura ou entrega.", - "howToUse": "Comece pelo Canvas de Hipótese de Automação. Referencie Jornada, Proposta de Valor, Domínio, Impacto de Negócio, Capacidade ou outras evidências apenas quando forem relevantes; não repita esses canvases aqui.", + "title": "Automation Hypothesis & Validation Canvas", + "purpose": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "howToUse": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", "sections": { "hypothesis": { - "section": "Hypothesis", - "description": "What do we believe automating which work for which actor will achieve? Use the form: We believe automating [work] for [actor] will achieve [outcome]." - }, - "supportingEvidence": { - "section": "Supporting evidence", - "description": "Which Journey, Value Proposition, Business Impact, Capacity, Domain, or other evidence supports this hypothesis? Link or reference existing artifacts instead of repeating them." + "section": "Automation hypothesis", + "description": "What work do we believe should be automated, and what outcome should it achieve?" }, - "automationScope": { - "section": "Scope of automation", - "description": "Which part of the work is being considered for automation now, and what is explicitly outside scope?" - }, - "responsibilityAndSolutionHypothesis": { - "section": "Hipótese inicial de implementação", - "description": "Qual é a suposição atual sobre como a automação poderia ser implementada? Esta é uma suposição a validar, não uma decisão de arquitetura." + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the hypothesis?" }, "criticalAssumptions": { "section": "Critical assumptions", - "description": "Which assumptions could invalidate value, feasibility, safety, operability, compliance, or adoption?" + "description": "What could make the hypothesis wrong, unsafe, or unworkable?" }, "validationExperiment": { "section": "Validation experiment", - "description": "What is the smallest useful PoC or investigation, what evidence and thresholds decide success, and what stop conditions apply?" + "description": "What is the smallest useful test, evidence threshold, and stop condition?" }, "decision": { "section": "Decision", - "description": "What is the evidence-based decision: supported, revise and retest, redesign the process first, or reject?" - } - } - }, - "humanAutomationResponsibilityCanvas": { - "title": "Human-Automation Responsibility Canvas", - "purpose": "Decide what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "howToUse": "List target process steps and decide the most appropriate performer for each step. Capture required oversight, escalation, and evidence so the solution does not assume every step should be automated.", - "sections": { - "processStep": { - "section": "Process step", - "description": "Which step in the target process is being assigned or reviewed?" - }, - "humanResponsibility": { - "section": "Human responsibility", - "description": "What should a person do, decide, approve, review, correct, or own?" - }, - "ruleOrWorkflowResponsibility": { - "section": "Rule or workflow responsibility", - "description": "What can be handled by deterministic rules, orchestration, routing, reminders, or scheduled workflow?" - }, - "agentOrAiResponsibility": { - "section": "Agent or AI responsibility", - "description": "What judgement, language, classification, generation, planning, or assistance may an agent or AI perform?" - }, - "apiOrSystemResponsibility": { - "section": "API or system responsibility", - "description": "What should be performed through system capability, API, event, connector, file, or direct integration?" - }, - "rpaOrUiAutomationResponsibility": { - "section": "RPA or UI automation responsibility", - "description": "Where is UI automation justified because no suitable system, API, event, connector, or data access path exists?" - }, - "requiredOversight": { - "section": "Required oversight", - "description": "What human supervision, approval, confirmation, monitoring, or review is required before or after the step?" - }, - "escalation": { - "section": "Escalation", - "description": "When should the step stop, ask for help, route to a person, or move to another support path?" - }, - "evidenceOrAuditTrail": { - "section": "Evidence or audit trail", - "description": "What record proves what happened, who or what acted, what data was used, and what decision was made?" + "description": "Proceed, revise, redesign the process, or stop?" } } }, "automationWorkflowCanvas": { - "title": "Canvas de Fluxo de Trabalho de Automação", - "purpose": "Desenhar a sequência, estados, dados, gatilhos, decisões, interações, caminhos de falha e recuperação do fluxo de trabalho de automação de ponta a ponta.", - "howToUse": "Use a alocação de responsabilidades do Canvas de Responsabilidade Humano-Automação como entrada. Foque em como o fluxo executa, muda de estado, troca dados, trata exceções, produz evidências e recupera.", + "title": "Automation Workflow Canvas", + "purpose": "Desenhar o fluxo de trabalho interno necessário para produzir os resultados selecionados para o cliente e para a capacidade.", + "howToUse": "Reutilize evidências da jornada do cliente, proposta de valor, domínio e validação. Defina o trabalho interno, distribua-o entre pessoas e automação e acrescente apenas os detalhes de execução.", "sections": { - "trigger": { - "section": "Trigger", - "description": "What event, schedule, user action, message, data change, or manual request starts the automation?" - }, - "inputs": { - "section": "Inputs", - "description": "What data, documents, messages, forms, records, or context are required at the start and during the workflow?" + "selectedCustomerCapabilityOutcomes": { + "section": "Resultados selecionados do cliente e da capacidade", + "description": "Que resultados acordados para o cliente e para a capacidade este fluxo deve produzir?" }, - "workflowStages": { - "section": "Workflow stages and states", - "description": "What are the main workflow stages and states from trigger to completion, including waiting, review, exception, and completion states?" + "internalWorkflowSteps": { + "section": "Etapas do fluxo de trabalho interno", + "description": "Que trabalho interno deve acontecer para produzir esses resultados?" }, - "decisionsAndRules": { - "section": "Decisions and rules", - "description": "Which deterministic rules, validations, thresholds, policies, or decision points shape the flow?" + "workAllocationHumanControl": { + "section": "Distribuição do trabalho e controlo humano", + "description": "O que permanece humano, o que é automatizado e onde são necessárias supervisão ou escalada?" }, - "agentActions": { - "section": "Automation actions", - "description": "What may the automation, workflow, rule, agent, integration, API, RPA, or system component do at each relevant stage?" + "inputsOutputsInteractions": { + "section": "Entradas, saídas e interações", + "description": "Que informações, sistemas e transferências são necessários?" }, - "systemInteractions": { - "section": "System interactions", - "description": "Which systems, APIs, events, connectors, custom components, files, or screens are called or updated?" + "decisionsExceptionsRecovery": { + "section": "Decisões, exceções e recuperação", + "description": "O que altera o fluxo, o que pode falhar e como o trabalho é recuperado?" }, - "dataSources": { - "section": "Data sources", - "description": "Which source systems, datasets, records, documents, or knowledge sources are used and trusted?" - }, - "humanTasks": { - "section": "Human checkpoints", - "description": "Where does the responsibility allocation require approval, confirmation, judgement, correction, review, or manual completion?" - }, - "handoffs": { - "section": "Handoffs and queues", - "description": "Where does work move between automation components, people, support teams, systems, queues, or exception paths?" - }, - "exceptions": { - "section": "Exceptions", - "description": "What error, missing-data, conflicting-data, timeout, permission, unsafe-action, or business exception scenarios must be handled?" - }, - "retriesAndTimeouts": { - "section": "Retries and timeouts", - "description": "Where are retries, timeout limits, duplicate prevention, idempotency, pause rules, or compensation required?" - }, - "outputs": { - "section": "Outputs", - "description": "What records, decisions, messages, documents, updates, notifications, or outcomes are produced?" - }, - "auditEvidence": { - "section": "Audit evidence", - "description": "What log, trace, approval, run history, input snapshot, output record, or explanation proves correct operation?" - }, - "monitoringPoints": { - "section": "Monitoring points", - "description": "Which run, failure, exception, latency, cost, intervention, quality, safety, or outcome metrics should be observed?" - }, - "recoveryPath": { - "section": "Recovery path", - "description": "How can the process be paused, rolled back, compensated, rerun, corrected, or completed manually?" + "evidenceMonitoring": { + "section": "Evidências e monitorização", + "description": "O que comprova o funcionamento correto e mostra se o resultado pretendido foi alcançado?" } } }, "automationArchitectureDecisionCanvas": { - "title": "Canvas de Decisão de Arquitetura de Automação", - "purpose": "Comparar e justificar mecanismos alternativos de implementação para uma solução de automação.", - "howToUse": "Marque cada mecanismo candidato como considerado, selecionado, rejeitado ou não relevante. Compare apenas os candidatos viáveis individualmente e como híbrido, depois justifique a abordagem recomendada com base em viabilidade, fiabilidade, segurança, manutenção, latência, escalabilidade, custo, dependências, testabilidade, observabilidade, recuperabilidade, competências e adequação arquitetural.", + "title": "Automation Architecture Decision Canvas", + "purpose": "Choose the implementation approach using evidence already gathered.", + "howToUse": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", "sections": { - "nativeFeature": { - "section": "Native feature", - "description": "Can an existing system capability solve this step with acceptable reliability, controls, and ownership?" - }, - "workflow": { - "section": "Workflow", - "description": "Where is workflow orchestration, scheduling, routing, approval, notification, or coordination the best fit?" - }, - "rule": { - "section": "Rule", - "description": "Which decisions can be implemented as deterministic business rules, policy checks, validations, or calculations?" - }, - "agent": { - "section": "Agent", - "description": "Where could an agent or AI safely add judgement, language understanding, generation, planning, or assistance?" - }, - "connector": { - "section": "Connector", - "description": "Which low-code, platform, SaaS, file, message, or data connectors are viable?" - }, - "api": { - "section": "API", - "description": "Where is an API call the best fit for reliable, governed, testable system interaction?" - }, - "event": { - "section": "Event", - "description": "Where should the solution react to, publish, or consume events?" - }, - "customCode": { - "section": "Custom code", - "description": "Where is custom code justified because standard capabilities are insufficient or too risky?" - }, - "rpa": { - "section": "RPA", - "description": "Where is desktop or UI automation justified, and what fragility or recovery controls are required?" - }, - "humanTask": { - "section": "Human task", - "description": "Which steps should remain human because of judgement, accountability, risk, consent, policy, or exception handling?" - }, - "feasibilityReliabilitySecurity": { - "section": "Feasibility, reliability, security", - "description": "How do candidates compare on technical feasibility, expected reliability, identity, authorization, data exposure, and control strength?" - }, - "maintainabilityScalabilityCost": { - "section": "Maintainability, scalability, cost", - "description": "How do candidates compare on change effort, operating cost, licence cost, transaction volume, peak load, and lifecycle maintenance?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which requirements, capacity, location, impact, and responsibility decisions constrain the choice?" }, - "latencyObservabilityRecoverability": { - "section": "Latency, observability, recoverability", - "description": "How do candidates compare on timing needs, monitoring, logs, traceability, retry, compensation, and manual recovery?" + "viableOptions": { + "section": "Viable options", + "description": "Which human, workflow, rule, agent, API, connector, custom, or UI automation options remain viable?" }, - "skillsVendorFit": { - "section": "Skills, vendor dependency, architectural fit", - "description": "What skills, ownership, platform dependencies, governance constraints, and architecture standards affect the decision?" - }, - "recommendedHybridApproach": { - "section": "Recommended hybrid approach", - "description": "Which combination of people, rules, workflows, agents, systems, APIs, events, custom code, and UI automation should be used?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style or hybrid is selected?" }, "decisionRationale": { "section": "Decision rationale", - "description": "Why is this approach preferred over the alternatives, and what evidence supports the decision?" + "description": "Why does the selected approach fit best?" + }, + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "openQuestionsAndRisks": { - "section": "Open questions and risks", - "description": "Which assumptions, risks, dependencies, or unresolved constraints must be validated before delivery or release?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "automationReadinessOperationsCanvas": { - "title": "Canvas de Prontidão e Operações da Automação", - "purpose": "Preparar o modelo operacional para uma automação lançada, suportada, monitorizada e recuperável com segurança.", - "howToUse": "Use this during delivery to prepare ownership, environments, access, evidence, monitoring, support, fallback, rollback, runbooks, known risks, and the deployment decision. Use the readiness checklist later for the release gate.", + "title": "Automation Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before readiness review.", + "howToUse": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Who accepts business value, process impact, residual risk, and release timing?" - }, - "operationalOwner": { - "section": "Operational owner", - "description": "Who owns runtime supervision, incidents, support, runbooks, changes, and recovery?" - }, - "users": { - "section": "Users", - "description": "Which users, operators, approvers, support teams, or process participants are affected?" + "ownership": { + "section": "Ownership", + "description": "Who owns business outcomes, operations, support, and changes?" }, - "permissions": { - "section": "Permissions", - "description": "What human, service, system, data, role, and approval permissions are required and approved?" - }, - "credentials": { - "section": "Credentials", - "description": "How are credentials, secrets, certificates, tokens, delegated access, and service identities managed?" - }, - "environments": { - "section": "Environments", - "description": "Which development, test, staging, production, desktop, cloud, or platform environments are used?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, permissions, credentials, and identities ready?" }, "testEvidence": { "section": "Test evidence", - "description": "What proves functional correctness, rule behavior, integration behavior, agent behavior, permissions, performance, and exceptions?" - }, - "exceptionHandling": { - "section": "Exception handling", - "description": "How are errors, missing data, unsafe actions, failed runs, retries, timeouts, and handoffs handled?" - }, - "monitoring": { - "section": "Monitoring", - "description": "Which run, failure, exception, latency, cost, intervention, value, safety, and outcome signals are monitored?" - }, - "support": { - "section": "Support", - "description": "Who supports users and operators, how are incidents raised, and what service expectations apply?" + "description": "What proves correct, safe, and reliable behavior?" }, - "manualFallback": { - "section": "Manual fallback", - "description": "How can work continue manually if the automation is paused, unavailable, incorrect, or unsafe?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, incidents, users, and operators be supported?" }, - "rollback": { - "section": "Rollback", - "description": "How can changes, actions, data updates, releases, or workflow versions be reversed or compensated?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will exceptions, fallback, rollback, and manual recovery work?" }, - "documentation": { - "section": "Documentation", - "description": "What operating instructions, design records, architecture decisions, user guidance, and runbooks are ready?" - }, - "deploymentDecision": { - "section": "Estado de prontidão para lançamento", - "description": "O que permanece incompleto, condicional ou bloqueante antes da decisão formal de prontidão?" - }, - "knownRisks": { - "section": "Known risks", - "description": "Which risks are accepted, mitigated, deferred, or blocking release?" - }, - "improvementBacklog": { - "section": "Improvement backlog", - "description": "Which improvements, unresolved assumptions, PoC findings, and future enhancements should be prioritized next?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are documentation, risks, conditions, and blocking gaps clear?" } } }, "integrationCapabilityHypothesisCanvas": { - "title": "Canvas de Hipótese de Capacidade de Integração", - "purpose": "Priorizar uma hipótese de capacidade de integração reutilizável ligando evidências de consumidores, valor, domínio, ownership, reutilização e viabilidade a um escopo claro, pressupostos, validação e decisão de avançar ou parar.", - "howToUse": "Comece aqui antes da escolha de arquitetura. Referencie evidências de jornada, proposta de valor, domínio, modelo de negócio, impacto, capacidade ou outras apenas quando sustentarem a hipótese.", + "title": "Integration Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable integration capability should proceed.", + "howToUse": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", "sections": { - "hypothesis": { - "section": "Hipótese de capacidade de integração", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Hipótese de capacidade de integração?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed integration capability and reuse scope are being tested?" }, - "consumersAndReuseScope": { - "section": "Consumidores previstos e escopo de reutilização", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Consumidores previstos e escopo de reutilização?" - }, - "providerAndOwner": { - "section": "Provider e owner", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Provider e owner?" - }, - "supportingEvidence": { - "section": "Evidências de suporte", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Evidências de suporte?" - }, - "implementationStyleHypothesis": { - "section": "Hipótese inicial de estilo de implementação", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Hipótese inicial de estilo de implementação?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { - "section": "Pressupostos críticos", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Pressupostos críticos?" + "section": "Critical assumptions", + "description": "What could invalidate value, reuse, ownership, feasibility, or adoption?" }, - "validationExperiment": { - "section": "Experiência de validação", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Experiência de validação?" + "validationStep": { + "section": "Validation step", + "description": "What is the smallest useful validation and success threshold?" }, "decision": { - "section": "Decisão", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Decisão?" + "section": "Decision", + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "integrationConsumerProviderRequirementsCanvas": { - "title": "Canvas de Requisitos do Consumidor e Provider de Integração", - "purpose": "Capturar o que sistemas consumidores, equipas, produtores, providers e operadores precisam antes de selecionar ou desenhar a implementação da integração.", - "howToUse": "Use isto para tornar explícitos onboarding, acesso, ambientes, identidade, compatibilidade, expectativas de serviço, qualidade dos dados, suporte e requisitos de recuperação.", + "title": "Integration Consumer & Provider Commitments Canvas", + "purpose": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "howToUse": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", "sections": { - "consumerSystemsAndTeams": { - "section": "Sistemas consumidores e equipas", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Sistemas consumidores e equipas?" - }, - "providerResponsibilities": { - "section": "Responsabilidades do provider", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Responsabilidades do provider?" - }, - "interactionAndDataNeeds": { - "section": "Necessidades de interação e dados", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Necessidades de interação e dados?" - }, - "onboardingAndAccess": { - "section": "Onboarding e acesso", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Onboarding e acesso?" + "selectedPartiesAndUseCases": { + "section": "Selected parties and use cases", + "description": "Which producers, providers, consumers, and use cases are covered?" }, - "environmentsAndTestAccess": { - "section": "Ambientes e acesso de teste", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Ambientes e acesso de teste?" + "providerCommitments": { + "section": "Provider commitments", + "description": "What will providers deliver, maintain, monitor, and support?" }, - "credentialsAndIdentity": { - "section": "Credenciais e identidade", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Credenciais e identidade?" + "consumerCommitments": { + "section": "Consumer commitments", + "description": "What must consumers test, protect, operate, and communicate?" }, - "compatibilityAndVersioning": { - "section": "Compatibilidade e versionamento", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Compatibilidade e versionamento?" + "accessAndValidationAgreement": { + "section": "Access and validation", + "description": "How will access, environments, credentials, and conformance be handled?" }, - "serviceExpectations": { - "section": "Expectativas de serviço", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Expectativas de serviço?" + "failureAndRecoveryAgreement": { + "section": "Failure and recovery", + "description": "Who handles failures, replay, duplicates, reconciliation, and recovery?" }, - "dataQualityAndObservability": { - "section": "Qualidade dos dados e observabilidade", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Qualidade dos dados e observabilidade?" - }, - "supportAndFailureHandling": { - "section": "Suporte e tratamento de falhas", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Suporte e tratamento de falhas?" - }, - "replayReconciliationRecovery": { - "section": "Replay, reconciliação, recuperação", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Replay, reconciliação, recuperação?" + "changeAndLifecycleAgreement": { + "section": "Change and lifecycle", + "description": "How will compatibility, migration, notice, deprecation, and retirement work?" } } }, "integrationArchitectureDecisionCanvas": { - "title": "Canvas de Decisão de Arquitetura de Integração", - "purpose": "Comparar e justificar estilos de implementação de integração, capacidades de plataforma, restrições de governação e alternativas rejeitadas.", - "howToUse": "Use o controlo de estado partilhado para marcar cada estilo candidato como considerado, selecionado, rejeitado ou não relevante. Compare opções viáveis por temporização, acoplamento, ownership dos dados, consistência, fiabilidade, segurança, manutenibilidade, observabilidade, recuperação, custo, governação e competências.", + "title": "Integration Architecture Decision Canvas", + "purpose": "Choose the integration style and platform using evidence already gathered.", + "howToUse": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", "sections": { - "synchronousApi": { - "section": "API síncrona", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para API síncrona?" - }, - "eventDriven": { - "section": "Evento assíncrono", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Evento assíncrono?" - }, - "messagingQueue": { - "section": "Mensageria ou fila", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Mensageria ou fila?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which commitments, capacity, location, impact, and domain decisions constrain the choice?" }, - "batchFileExchange": { - "section": "Troca batch ou ficheiro", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Troca batch ou ficheiro?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, messaging, file, stream, data, connector, platform, or custom options remain viable?" }, - "stream": { - "section": "Stream", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Stream?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which integration style, platform, or hybrid is selected?" }, - "etlElt": { - "section": "ETL ou ELT", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para ETL ou ELT?" - }, - "dataProduct": { - "section": "Produto de dados", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Produto de dados?" - }, - "directDatabase": { - "section": "Integração direta com base de dados", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Integração direta com base de dados?" - }, - "sharedPlatform": { - "section": "Plataforma de integração partilhada", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Plataforma de integração partilhada?" - }, - "pointToPoint": { - "section": "Point-to-point", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Point-to-point?" - }, - "managedConnector": { - "section": "Connector gerido", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Connector gerido?" - }, - "customIntegration": { - "section": "Integração customizada", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Integração customizada?" - }, - "hybridApproach": { - "section": "Abordagem híbrida", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Abordagem híbrida?" - }, - "evaluationCriteria": { - "section": "Critérios de avaliação", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Critérios de avaliação?" - }, - "selectedStyleAndPlatform": { - "section": "Estilo e plataforma selecionados", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Estilo e plataforma selecionados?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "rationaleAndRejectedAlternatives": { - "section": "Justificação e alternativas rejeitadas", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Justificação e alternativas rejeitadas?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "openRisksAndAssumptions": { - "section": "Riscos e pressupostos em aberto", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Riscos e pressupostos em aberto?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "integrationReadinessOperationsCanvas": { - "title": "Canvas de Prontidão e Operações da Integração", - "purpose": "Preparar o modelo operacional para uma capacidade de integração reutilizável lançada, suportada, monitorizada e recuperável com segurança.", - "howToUse": "Use isto durante a entrega para preparar ownership, ambientes, credenciais, deployment, monitorização, suporte, retry, replay, reconciliação, fallback, rollback, incidentes, evidências de teste, riscos e estado de prontidão.", + "title": "Integration Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before integration readiness review.", + "howToUse": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Business owner?" - }, - "integrationOwner": { - "section": "Owner da integração", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Owner da integração?" - }, - "producerOwners": { - "section": "Owners produtores", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Owners produtores?" - }, - "consumerOwners": { - "section": "Owners consumidores", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Owners consumidores?" - }, - "platformOwner": { - "section": "Owner da plataforma", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Owner da plataforma?" - }, - "environments": { - "section": "Ambientes", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Ambientes?" - }, - "credentials": { - "section": "Credenciais", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Credenciais?" - }, - "deployment": { - "section": "Deployment", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Deployment?" - }, - "monitoring": { - "section": "Monitorização", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Monitorização?" - }, - "support": { - "section": "Suporte", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Suporte?" + "ownership": { + "section": "Ownership", + "description": "Who owns business, integration, producer, consumer, platform, and incident responsibilities?" }, - "retryReplay": { - "section": "Retry e replay", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Retry e replay?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are environments, credentials, connectivity, permissions, and sequencing ready?" }, - "reconciliation": { - "section": "Reconciliação", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Reconciliação?" - }, - "fallbackRollback": { - "section": "Fallback e rollback", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Fallback e rollback?" - }, - "incidentOwnership": { - "section": "Ownership de incidentes", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Ownership de incidentes?" + "testEvidence": { + "section": "Test evidence", + "description": "What proves contract, mapping, compatibility, quality, resilience, and recovery?" }, - "testEvidenceKnownRisks": { - "section": "Evidências de teste e riscos conhecidos", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Evidências de teste e riscos conhecidos?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will producers, consumers, platforms, incidents, and service questions be supported?" }, - "readinessStatus": { - "section": "Estado de prontidão", - "description": "Que informação, evidências, decisões e pontos em aberto devem ser registados para Estado de prontidão?" + "failureAndRecovery": { + "section": "Failure and recovery", + "description": "How will retry, replay, duplicates, reconciliation, fallback, and compensation work?" }, - "documentationDependenciesChangeReadiness": { - "section": "Documentação, dependências e prontidão de mudança", - "description": "Contratos, mapeamentos, runbooks, dependências, instruções de migração, sequência de deployment, cutover, compatibilidade retroativa, ownership de versões e responsabilidades de mudança estão prontos?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are contracts, runbooks, dependencies, risks, conditions, and blocking gaps clear?" } } }, "integrationSolutionDesignCanvas": { - "title": "Canvas de Desenho da Solução de Integração", - "purpose": "Resume o desenho completo da integração entre estilos de implementação, incluindo contratos, esquemas, estruturas de dados, mapeamentos, comportamento de entrega, segurança, erros, observabilidade, reconciliação e versionamento.", - "howToUse": "Use isto como artefacto principal de desenho da solução após a decisão de arquitetura. Use Interaction Canvas, REST, Event, GraphQL, ficheiro, stream, produto de dados ou mensageria como apoio detalhado condicional.", + "title": "Integration Solution Design Canvas", + "purpose": "Refine the selected architecture into an implementable integration design.", + "howToUse": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", "sections": { - "selectedIntegrationStyle": { - "section": "Estilo de integração selecionado", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Estilo de integração selecionado?" - }, - "producerAndConsumer": { - "section": "Produtor e consumidor", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Produtor e consumidor?" - }, - "contractAndSchema": { - "section": "Contrato e esquema", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Contrato e esquema?" - }, - "mappingsAndTransformations": { - "section": "Mapeamentos e transformações", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Mapeamentos e transformações?" - }, - "interactionDeliveryPattern": { - "section": "Padrão de interação ou entrega", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Padrão de interação ou entrega?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which architecture, domain, interaction, and commitment decisions are reused?" }, - "identityAndSecurity": { - "section": "Identidade e segurança", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Identidade e segurança?" + "contractAndModel": { + "section": "Contract and model", + "description": "What contract, schema, data model, and version define the integration?" }, - "errorRetryReplay": { - "section": "Modelo de erro, retry, replay", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Modelo de erro, retry, replay?" + "mappingAndDelivery": { + "section": "Mapping and delivery", + "description": "What transformations, delivery pattern, and metadata are required?" }, - "correlationMetadata": { - "section": "Correlação e metadados", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Correlação e metadados?" + "errorsAndRecovery": { + "section": "Errors and recovery", + "description": "How are failures, retries, replay, duplicates, and reconciliation handled?" }, - "reconciliationRules": { - "section": "Regras de reconciliação", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Regras de reconciliação?" + "securityAndTrust": { + "section": "Security and trust", + "description": "What identity, access, privacy, and trust controls apply?" }, - "observability": { - "section": "Observabilidade", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Observabilidade?" - }, - "versioningEvolution": { - "section": "Versionamento e evolução", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Versionamento e evolução?" - }, - "canonicalConsumerSpecificModel": { - "section": "Modelo canónico vs específico do consumidor", - "description": "Que decisões de desenho, regras, evidências e pontos em aberto devem ser registados para Modelo canónico vs específico do consumidor?" + "observabilityAndEvolution": { + "section": "Observability and evolution", + "description": "How will the integration be monitored, changed, migrated, and deprecated?" } } }, "capabilityHypothesisCanvas": { - "title": "Canvas de Hipótese de Capacidade", - "purpose": "Priorizar uma hipótese de capacidade digital reutilizável ligando evidências de consumidor, valor, domínio, ownership, viabilidade e reutilização a um escopo claro, pressupostos, validação e decisão.", - "howToUse": "Que decisões, evidências e pontos em aberto devem ser registados para Canvas de Hipótese de Capacidade?", + "title": "Capability Validation Canvas", + "purpose": "Validate whether a proposed reusable digital capability should proceed.", + "howToUse": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", "sections": { - "hypothesis": { - "section": "Hipótese de capacidade", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Hipótese de capacidade?" - }, - "targetConsumersUseCases": { - "section": "Consumidores-alvo e casos de uso", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Consumidores-alvo e casos de uso?" + "capabilityToValidate": { + "section": "Capability to validate", + "description": "Which proposed capability and reusable scope are being tested?" }, - "reusableScope": { - "section": "Escopo reutilizável previsto", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Escopo reutilizável previsto?" - }, - "supportingEvidence": { - "section": "Evidências de suporte", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Evidências de suporte?" - }, - "expectedOutcomes": { - "section": "Resultados esperados", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Resultados esperados?" + "reusedEvidence": { + "section": "Reused evidence", + "description": "Which earlier canvas outputs support the proposal?" }, "criticalAssumptions": { - "section": "Pressupostos críticos", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Pressupostos críticos?" + "section": "Critical assumptions", + "description": "What could invalidate value, reuse, ownership, sustainability, or adoption?" }, "minimumValidation": { - "section": "Validação mínima", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Validação mínima?" + "section": "Minimum validation", + "description": "What is the smallest useful validation and success threshold?" }, "decision": { - "section": "Decisão", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Decisão?" + "section": "Decision", + "description": "Proceed, narrow, revise and retest, or stop?" } } }, "capabilityConsumerProducerRequirementsCanvas": { - "title": "Canvas de Requisitos do Consumidor e Produtor", - "purpose": "Capturar o que consumidores, produtores, owners, operadores e equipas de suporte precisam de uma capacidade reutilizável antes de selecionar ou desenhar o estilo de implementação.", - "howToUse": "Que decisões, evidências e pontos em aberto devem ser registados para Canvas de Requisitos do Consumidor e Produtor?", + "title": "Capability Consumer & Producer Commitments Canvas", + "purpose": "Agree mutual commitments for providing and consuming a reusable capability.", + "howToUse": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", "sections": { - "intendedConsumersContexts": { - "section": "Consumidores e contextos previstos", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Consumidores e contextos previstos?" + "selectedConsumersAndUseCases": { + "section": "Selected consumers and use cases", + "description": "Which consumers and usage contexts are covered?" }, - "capabilityOwnerProducerResponsibilities": { - "section": "Owner da capacidade e responsabilidades do produtor", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Owner da capacidade e responsabilidades do produtor?" + "ownerAndProducerCommitments": { + "section": "Owner and producer commitments", + "description": "What will owners and producers provide, maintain, monitor, and support?" }, - "discoveryEvaluation": { - "section": "Descoberta e avaliação", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Descoberta e avaliação?" - }, - "accessOnboarding": { - "section": "Acesso e onboarding", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Acesso e onboarding?" - }, - "serviceExpectations": { - "section": "Expectativas de serviço", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Expectativas de serviço?" - }, - "qualityAvailability": { - "section": "Expectativas de qualidade e disponibilidade", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Expectativas de qualidade e disponibilidade?" - }, - "changeLifecycle": { - "section": "Expectativas de mudança e ciclo de vida", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Expectativas de mudança e ciclo de vida?" - }, - "supportIncidentCommunication": { - "section": "Suporte e comunicação de incidentes", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Suporte e comunicação de incidentes?" - }, - "operationalGovernanceConstraints": { - "section": "Restrições operacionais e de governação", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Restrições operacionais e de governação?" + "consumerResponsibilities": { + "section": "Consumer responsibilities", + "description": "What must consumers do for appropriate use, access, testing, and feedback?" }, - "producerCommitments": { - "section": "Compromissos do produtor", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Compromissos do produtor?" + "accessAndOnboardingAgreement": { + "section": "Access and onboarding", + "description": "What discovery, approval, testing, and onboarding path is agreed?" }, - "consumerResponsibilities": { - "section": "Responsabilidades do consumidor", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Responsabilidades do consumidor?" + "serviceAndLifecycleAgreement": { + "section": "Service and lifecycle", + "description": "What service, change, deprecation, and retirement commitments are agreed?" }, - "architectureImplications": { - "section": "Implicações de arquitetura", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Implicações de arquitetura?" + "openCommitments": { + "section": "Open commitments", + "description": "What remains unresolved before architecture or delivery?" } } }, "capabilityArchitectureDecisionCanvas": { - "title": "Canvas de Decisão de Arquitetura de Capacidade", - "purpose": "Comparar opções de implementação e registar o estilo de implementação da capacidade selecionado, plataforma, justificação, alternativas rejeitadas, pressupostos e riscos.", - "howToUse": "Use o controlo de estado partilhado para marcar cada estilo candidato como considerado, selecionado, rejeitado ou não relevante. Compare opções por necessidades dos consumidores, reutilização, acoplamento, latência, temporização, volume, ownership dos dados, consistência, segurança, fronteiras de confiança e localização, fiabilidade, operabilidade, custo, competências, fit de plataforma, governação, descoberta e gestão de ciclo de vida.", + "title": "Capability Architecture Decision Canvas", + "purpose": "Choose how the capability will be delivered using evidence already gathered.", + "howToUse": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", "sections": { - "api": { - "section": "API", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para API?" - }, - "event": { - "section": "Evento", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Evento?" - }, - "fileBatch": { - "section": "Ficheiro ou batch", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Ficheiro ou batch?" - }, - "stream": { - "section": "Stream", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Stream?" - }, - "dataProduct": { - "section": "Produto de dados", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Produto de dados?" - }, - "workflow": { - "section": "Workflow", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Workflow?" - }, - "sharedService": { - "section": "Serviço partilhado", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Serviço partilhado?" - }, - "userFacingApplication": { - "section": "Aplicação orientada ao utilizador", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Aplicação orientada ao utilizador?" - }, - "directIntegration": { - "section": "Integração direta", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Integração direta?" + "reusedInputs": { + "section": "Reused inputs", + "description": "Which earlier decisions and constraints shape the implementation choice?" }, - "platformNativeFeature": { - "section": "Funcionalidade nativa da plataforma", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Funcionalidade nativa da plataforma?" + "viableOptions": { + "section": "Viable options", + "description": "Which API, event, workflow, application, data product, shared service, human service, or hybrid options remain viable?" }, - "humanAssistedService": { - "section": "Serviço assistido por humano", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Serviço assistido por humano?" - }, - "hybridApproach": { - "section": "Abordagem híbrida", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Abordagem híbrida?" - }, - "evaluationCriteria": { - "section": "Critérios de avaliação", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Critérios de avaliação?" + "selectedApproach": { + "section": "Selected approach", + "description": "Which implementation style and enabling platform are selected?" }, - "selectedStylePlatform": { - "section": "Estilo e plataforma selecionados", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Estilo e plataforma selecionados?" + "decisionRationale": { + "section": "Decision rationale", + "description": "Why does the selected approach fit best?" }, - "rationaleRejectedAlternatives": { - "section": "Justificação e alternativas rejeitadas", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Justificação e alternativas rejeitadas?" + "rejectedAlternatives": { + "section": "Rejected alternatives", + "description": "Which serious alternatives were rejected, and why?" }, - "assumptionsRisks": { - "section": "Pressupostos e riscos", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Pressupostos e riscos?" + "openRisks": { + "section": "Open risks", + "description": "What still needs validation before delivery or release?" } } }, "capabilitySolutionDesignCanvas": { - "title": "Canvas de Desenho da Solução de Capacidade", - "purpose": "Desenhar como consumidores acedem, interagem, recebem ou usam a capacidade através do estilo de implementação selecionado.", - "howToUse": "Que decisões, evidências e pontos em aberto devem ser registados para Canvas de Desenho da Solução de Capacidade?", + "title": "Capability Solution Design Canvas", + "purpose": "Refine the selected implementation style into a clear consumer-facing capability design.", + "howToUse": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", "sections": { - "selectedImplementationStyle": { - "section": "Estilo de implementação selecionado", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Estilo de implementação selecionado?" - }, - "serviceBoundary": { - "section": "Fronteira do serviço", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Fronteira do serviço?" - }, - "consumerInteractionModel": { - "section": "Modelo de interação do consumidor", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Modelo de interação do consumidor?" - }, - "dataBusinessConcepts": { - "section": "Conceitos de dados e negócio", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Conceitos de dados e negócio?" - }, - "contractOrServiceDefinition": { - "section": "Contrato ou definição de serviço", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Contrato ou definição de serviço?" + "selectedInputs": { + "section": "Selected inputs", + "description": "Which earlier journey, value, domain, commitment, and architecture decisions are reused?" }, - "responsibilitiesRules": { - "section": "Responsabilidades e regras", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Responsabilidades e regras?" + "boundaryAndInteraction": { + "section": "Boundary and interaction", + "description": "What belongs inside the capability, and how do consumers use it?" }, - "inputsOutputs": { - "section": "Entradas e saídas", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Entradas e saídas?" - }, - "errorsExceptions": { - "section": "Erros e exceções", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Erros e exceções?" + "contractRulesAndOutcomes": { + "section": "Contract, rules, and outcomes", + "description": "What behavior, responsibilities, inputs, outputs, and outcomes are promised?" }, - "lifecycleVersioning": { - "section": "Ciclo de vida e versionamento", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Ciclo de vida e versionamento?" + "errorsAndSecurity": { + "section": "Errors and security", + "description": "How are exceptions, access, privacy, and trust handled?" }, - "securityPrivacy": { - "section": "Segurança e privacidade", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Segurança e privacidade?" + "lifecycleAndSupport": { + "section": "Lifecycle and support", + "description": "How will change, versioning, support, deprecation, and retirement work?" }, "observability": { - "section": "Observabilidade", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Observabilidade?" - }, - "supportModel": { - "section": "Modelo de suporte", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Modelo de suporte?" + "section": "Observability", + "description": "What health, usage, quality, value, and consumer signals must be visible?" } } }, "capabilityReadinessOperationsCanvas": { - "title": "Canvas de Prontidão e Operações da Capacidade", - "purpose": "Preparar o modelo operacional de uma capacidade reutilizável antes da decisão formal de prontidão.", - "howToUse": "Que decisões, evidências e pontos em aberto devem ser registados para Canvas de Prontidão e Operações da Capacidade?", + "title": "Capability Readiness & Operations Canvas", + "purpose": "Prepare the minimum operating evidence needed before capability readiness review.", + "howToUse": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", "sections": { - "businessOwner": { - "section": "Business owner", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Business owner?" - }, - "capabilityOwner": { - "section": "Owner da capacidade", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Owner da capacidade?" - }, - "producerOwner": { - "section": "Owner produtor", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Owner produtor?" - }, - "operationalOwner": { - "section": "Owner operacional", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Owner operacional?" - }, - "consumers": { - "section": "Consumidores", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Consumidores?" + "ownership": { + "section": "Ownership", + "description": "Who owns value, the capability lifecycle, production, operations, support, and changes?" }, - "implementationStyle": { - "section": "Estilo de implementação", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Estilo de implementação?" - }, - "environments": { - "section": "Ambientes", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Ambientes?" - }, - "permissionsCredentials": { - "section": "Permissões e credenciais", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Permissões e credenciais?" + "environmentsAndAccess": { + "section": "Environments and access", + "description": "Are required environments, access, permissions, and credentials ready?" }, "testEvidence": { - "section": "Evidências de teste", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Evidências de teste?" - }, - "serviceExpectations": { - "section": "Expectativas de serviço", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Expectativas de serviço?" - }, - "monitoring": { - "section": "Monitorização", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Monitorização?" - }, - "support": { - "section": "Suporte", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Suporte?" - }, - "fallbackContinuity": { - "section": "Fallback e continuidade", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Fallback e continuidade?" - }, - "changeOwnership": { - "section": "Ownership da mudança", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Ownership da mudança?" - }, - "documentationRunbooks": { - "section": "Documentação e runbooks", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Documentação e runbooks?" + "section": "Test evidence", + "description": "What proves outcomes, quality, security, compatibility, resilience, and consumer usability?" }, - "readinessStatus": { - "section": "Estado de prontidão", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Estado de prontidão?" + "monitoringAndSupport": { + "section": "Monitoring and support", + "description": "How will health, usage, value, incidents, consumers, and operators be supported?" }, - "knownRisks": { - "section": "Riscos conhecidos", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Riscos conhecidos?" + "failureAndRecovery": { + "section": "Continuity and recovery", + "description": "How will service continue, degrade safely, recover, or fall back?" }, - "improvementBacklog": { - "section": "Backlog de melhoria", - "description": "Que decisões concretas, evidências, responsabilidades, riscos e próximos passos devem ser registados para Backlog de melhoria?" + "documentationRisksAndReadiness": { + "section": "Readiness status", + "description": "Are service definitions, runbooks, risks, conditions, and blocking gaps clear?" } } } diff --git a/src/data/method/cycles.json b/src/data/method/cycles.json index e6f3353..b1f9855 100644 --- a/src/data/method/cycles.json +++ b/src/data/method/cycles.json @@ -12,54 +12,61 @@ "description": "cycle.capability-productization-cycle.description", "purpose": "cycle.capability-productization-cycle.purpose", "stations": [ - "capability-strategy", - "capability-consumer-producer-requirements", - "capability-architecture-platform-decisions", - "capability-solution-interaction-design", - "capability-delivery-operations", - "capability-readiness-assurance", - "capability-publishing-enablement", - "capability-monitoring-improvement" + "api-product-strategy", + "api-consumer-experience", + "api-platform-architecture", + "api-design", + "api-delivery", + "api-audit", + "api-publishing", + "monitoring-and-improving" ], "stationLabels": { - "capability-strategy": "cycle.station.capability-strategy", - "capability-consumer-producer-requirements": "cycle.station.consumer-producer-service-requirements", - "capability-architecture-platform-decisions": "cycle.station.capability-architecture-platform-decisions", - "capability-solution-interaction-design": "cycle.station.capability-solution-interaction-design", - "capability-delivery-operations": "cycle.station.capability-delivery-operations", - "capability-readiness-assurance": "cycle.station.capability-readiness-assurance", - "capability-publishing-enablement": "cycle.station.capability-publishing-enablement", - "capability-monitoring-improvement": "cycle.station.capability-monitoring-improvement" + "api-product-strategy": "cycle.station.capability-strategy", + "api-consumer-experience": "cycle.station.consumer-producer-service-requirements", + "api-platform-architecture": "cycle.station.capability-architecture-platform-decisions", + "api-design": "cycle.station.capability-solution-interaction-design", + "api-delivery": "cycle.station.capability-delivery-operations", + "api-audit": "cycle.station.capability-readiness-assurance", + "api-publishing": "cycle.station.capability-publishing-enablement", + "monitoring-and-improving": "cycle.station.capability-monitoring-improvement" }, "stationDescriptions": { - "capability-strategy": "cycle.capability-productization-cycle.station.capability-strategy.description", - "capability-consumer-producer-requirements": "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description", - "capability-architecture-platform-decisions": "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description", - "capability-solution-interaction-design": "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description", - "capability-delivery-operations": "cycle.capability-productization-cycle.station.capability-delivery-operations.description", - "capability-readiness-assurance": "cycle.capability-productization-cycle.station.capability-readiness-assurance.description", - "capability-publishing-enablement": "cycle.capability-productization-cycle.station.capability-publishing-enablement.description", - "capability-monitoring-improvement": "cycle.capability-productization-cycle.station.capability-monitoring-improvement.description" + "api-product-strategy": "cycle.capability-productization-cycle.station.capability-strategy.description", + "api-consumer-experience": "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description", + "api-platform-architecture": "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description", + "api-design": "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description", + "api-delivery": "cycle.capability-productization-cycle.station.capability-delivery-operations.description", + "api-audit": "cycle.capability-productization-cycle.station.capability-readiness-assurance.description", + "api-publishing": "cycle.capability-productization-cycle.station.capability-publishing-enablement.description", + "monitoring-and-improving": "cycle.capability-productization-cycle.station.capability-monitoring-improvement.description" }, "recommendedResources": { - "capability-strategy": [ + "api-product-strategy": [ + "customerJourneyCanvas", + "capabilityValuePropositionCanvas", + "capabilityBusinessModelCanvas", "capabilityHypothesisCanvas" ], - "capability-consumer-producer-requirements": [ + "api-consumer-experience": [ "capabilityConsumerProducerRequirementsCanvas", "capability-consumer-onboarding-guide", "capability-service-expectations-guide", "capability-ownership-producer-responsibilities-guide" ], - "capability-architecture-platform-decisions": [ + "api-platform-architecture": [ + "businessImpactCanvas", + "locationsCanvas", + "capacityCanvas", "capabilityArchitectureDecisionCanvas" ], - "capability-solution-interaction-design": [ + "api-design": [ + "domainCanvas", "capabilitySolutionDesignCanvas", "interactionCanvas", "contract-first-design" ], - "capability-delivery-operations": [ + "api-delivery": [ "capabilityReadinessOperationsCanvas", "capability-delivery-guide", "capability-testing-validation-guide", @@ -68,18 +75,18 @@ "capability-security-access-guide", "capability-support-lifecycle-guide" ], - "capability-readiness-assurance": [ + "api-audit": [ "capability-readiness-checklist", "capability-compliance-governance-guide", "capability-service-quality-checklist" ], - "capability-publishing-enablement": [ + "api-publishing": [ "capability-publishing-discovery-guide", "capability-consumer-onboarding-guide", "capability-service-agreement-template", "capability-versioning-lifecycle-guide" ], - "capability-monitoring-improvement": [ + "monitoring-and-improving": [ "capability-monitoring-value-metrics", "capability-adoption-reuse-guide", "capability-consumer-feedback-guide", @@ -197,44 +204,51 @@ "description": "cycle.integration-productization-cycle.description", "purpose": "cycle.integration-productization-cycle.purpose", "stations": [ - "integration-capability-strategy", - "integration-consumer-requirements-onboarding", - "integration-architecture-platform-decisions", - "integration-solution-design", - "integration-delivery-operations", - "integration-readiness-assurance", - "integration-publishing-enablement", - "integration-monitoring-improvement" + "api-product-strategy", + "api-consumer-experience", + "api-platform-architecture", + "api-design", + "api-delivery", + "api-audit", + "api-publishing", + "monitoring-and-improving" ], "stationLabels": { - "integration-capability-strategy": "cycle.station.integration-capability-strategy", - "integration-consumer-requirements-onboarding": "cycle.station.integration-consumer-requirements-onboarding", - "integration-architecture-platform-decisions": "cycle.station.integration-architecture-decision", - "integration-solution-design": "cycle.station.integration-solution-design", - "integration-delivery-operations": "cycle.station.integration-delivery-operations", - "integration-readiness-assurance": "cycle.station.integration-readiness-assurance", - "integration-publishing-enablement": "cycle.station.capability-publishing", - "integration-monitoring-improvement": "cycle.station.integration-monitoring-improvement" + "api-product-strategy": "cycle.station.integration-capability-strategy", + "api-consumer-experience": "cycle.station.integration-consumer-requirements-onboarding", + "api-platform-architecture": "cycle.station.integration-architecture-decision", + "api-design": "cycle.station.integration-solution-design", + "api-delivery": "cycle.station.integration-delivery-operations", + "api-audit": "cycle.station.integration-readiness-assurance", + "api-publishing": "cycle.station.capability-publishing", + "monitoring-and-improving": "cycle.station.integration-monitoring-improvement" }, "recommendedResources": { - "integration-capability-strategy": [ + "api-product-strategy": [ + "customerJourneyCanvas", + "capabilityValuePropositionCanvas", + "capabilityBusinessModelCanvas", "integrationCapabilityHypothesisCanvas" ], - "integration-consumer-requirements-onboarding": [ + "api-consumer-experience": [ "integrationConsumerProviderRequirementsCanvas", "integration-consumer-onboarding-guide", "integration-access-environment-checklist" ], - "integration-architecture-platform-decisions": [ + "api-platform-architecture": [ + "businessImpactCanvas", + "locationsCanvas", + "capacityCanvas", "integrationArchitectureDecisionCanvas" ], - "integration-solution-design": [ + "api-design": [ + "domainCanvas", "integrationSolutionDesignCanvas", "interactionCanvas", "contract-first-design", "integration-style-design-guide" ], - "integration-delivery-operations": [ + "api-delivery": [ "integrationReadinessOperationsCanvas", "integration-development-best-practices", "integration-testing-guide", @@ -242,17 +256,17 @@ "integration-security-guide", "integration-recovery-reconciliation-guide" ], - "integration-readiness-assurance": [ + "api-audit": [ "integration-readiness-checklist", "integration-compliance-data-governance-guide" ], - "integration-publishing-enablement": [ + "api-publishing": [ "integration-publishing-discovery-guide", "integration-consumer-onboarding-guide", "integration-service-agreement-template", "integration-versioning-deprecation-guide" ], - "integration-monitoring-improvement": [ + "monitoring-and-improving": [ "integration-monitoring-value-metrics", "integration-consumer-feedback-adoption-guide", "integration-reliability-data-quality-metrics", @@ -269,14 +283,14 @@ "integration-published-for-reuse" ], "stationDescriptions": { - "integration-capability-strategy": "cycle.integration-productization-cycle.station.integration-capability-strategy.description", - "integration-consumer-requirements-onboarding": "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description", - "integration-architecture-platform-decisions": "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description", - "integration-solution-design": "cycle.integration-productization-cycle.station.integration-solution-design.description", - "integration-delivery-operations": "cycle.integration-productization-cycle.station.integration-delivery-operations.description", - "integration-readiness-assurance": "cycle.integration-productization-cycle.station.integration-readiness-assurance.description", - "integration-publishing-enablement": "cycle.integration-productization-cycle.station.integration-publishing-enablement.description", - "integration-monitoring-improvement": "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description" + "api-product-strategy": "cycle.integration-productization-cycle.station.integration-capability-strategy.description", + "api-consumer-experience": "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description", + "api-platform-architecture": "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description", + "api-design": "cycle.integration-productization-cycle.station.integration-solution-design.description", + "api-delivery": "cycle.integration-productization-cycle.station.integration-delivery-operations.description", + "api-audit": "cycle.integration-productization-cycle.station.integration-readiness-assurance.description", + "api-publishing": "cycle.integration-productization-cycle.station.integration-publishing-enablement.description", + "monitoring-and-improving": "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description" } }, { @@ -307,13 +321,18 @@ }, "recommendedResources": { "api-product-strategy": [ + "customerJourneyCanvas", + "capabilityValuePropositionCanvas", "automationOpportunityCanvas" ], "api-consumer-experience": [ - "humanAutomationResponsibilityCanvas", - "userOperatorExperienceRequirementsCanvas" + "consumerExperienceRequirementsCanvas", + "domainCanvas" ], "api-platform-architecture": [ + "businessImpactCanvas", + "locationsCanvas", + "capacityCanvas", "automationArchitectureDecisionCanvas" ], "api-design": [ diff --git a/src/data/method/de/labels.cycles.json b/src/data/method/de/labels.cycles.json index c1f5af3..9b12c3c 100644 --- a/src/data/method/de/labels.cycles.json +++ b/src/data/method/de/labels.cycles.json @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "API-Veröffentlichung", "cycle.station.monitoring-and-improving": "API-Monitoring & Verbesserung", "cycle.station.integration-capability-strategy": "Integrations-Capability-Strategie", - "cycle.station.integration-consumer-requirements-onboarding": "Integrationsnutzeranforderungen & Onboarding", + "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", "cycle.station.integration-architecture-decision": "Integrationsarchitektur & Plattformentscheidungen", "cycle.station.integration-solution-design": "Integrationsdesign", "cycle.station.integration-delivery-operations": "Integrationsbereitstellung & Betrieb", @@ -47,7 +47,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Überwachen Sie API-Gesundheit, Adoption, Nutzerergebnisse, Zuverlässigkeit und Verbesserungsmöglichkeiten nach der Veröffentlichung.", "cycle.automation-cycle.title": "Automatisierungszyklus", "cycle.automation-cycle.description": "Ein Zyklus zum Auswählen, Entwerfen, Bereitstellen, Einführen und Verbessern von Automatisierungslösungen über Menschen, Regeln, Workflows, Agenten, Integrationen, UI-Automatisierung und Betrieb hinweg.", - "cycle.automation-cycle.purpose": "Guide teams from a validated automation opportunity to a governed, operable automation solution by deciding what each step should be performed by: a person, rule, workflow, agent, API or system integration, connector, custom code, or UI automation.", + "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", "cycle.audience.automation-owners": "Automation Owner", "cycle.audience.process-owners": "Prozessverantwortliche", "cycle.audience.automation-teams": "Automatisierungsteams", @@ -57,33 +57,33 @@ "cycle.station.automation-readiness-review": "Automatisierungsbereitschaftsprüfung", "cycle.station.automation-enablement": "Automatisierungs-Rollout & Enablement", "cycle.station.automation-monitoring-improvement": "Automatisierungsmonitoring & Verbesserung", - "cycle.automation-cycle.station.api-product-strategy.description": "Prioritize a testable automation hypothesis. Use Customer Journey, Capability Value Proposition, Domain, Business Impact, Capacity, or other canvases only as optional supporting evidence where relevant.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Create the initial human-automation responsibility allocation and capture user, operator, permission, activation, support, recovery, observability, and non-functional requirements before implementation choices are made.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Evaluate and justify the automation architecture and implementation approach against requirements, responsibility assumptions, feasibility, security, reliability, operability, cost, and risk.", - "cycle.automation-cycle.station.api-design.description": "Design the automation workflow sequence, states, triggers, data, decisions, system interactions, handoffs, exceptions, evidence, monitoring points, and recovery paths.", + "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", + "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", "cycle.automation-cycle.station.api-audit.description": "Nutzen Sie eine Readiness-Checkliste, um Nachweise zu prüfen und die Freigabeentscheidung festzuhalten: bereit, unter Bedingungen bereit, Nachbesserung erforderlich oder nicht genehmigt.", "cycle.automation-cycle.station.api-publishing.description": "Aktivieren und rollen Sie die Automatisierung sicher aus - mit Kommunikation, Schulung, Betriebsanweisungen, Supportwegen, Adoptionsmonitoring, Feedbackkanälen, phasenweisem Rollout sowie Pausen- und Rollback-Bedingungen.", "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process, User & Automation Requirements", + "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Priorisieren Sie eine wiederverwendbare Integrationsfähigkeitshypothese mit Verbraucher-, Wert-, Domänen-, Ownership-, Wiederverwendungs- und Viabilitätsnachweisen.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Erfassen Sie Integrations-Consumer, Provider-Verantwortlichkeiten, Onboarding-Bedarfe, Serviceerwartungen und operative Randbedingungen.", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Wählen Sie Integrationsarchitektur, Implementierungsstil und Plattformfähigkeiten unter Berücksichtigung von Randbedingungen und Governance.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Entwerfen Sie Integrationslösung, Verträge, Schemas, Datenstrukturen, Mappings sowie Interaktions- oder Liefermuster für den ausgewählten Stil.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Bauen, testen, deployen und betreiben Sie die Integrationsfähigkeit mit ausgewähltem Implementierungsstil und validiertem Vertrag.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Sichern Sie Integrations-Readiness, Governance, Qualität, Security, Compliance und operative Nachweise vor der Freigabe ab.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Veröffentlichen Sie die Integrationsfähigkeit, damit Teams sie finden, bewerten, Zugriff beantragen, onboarding durchführen, wiederverwenden und Support erhalten können.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Überwachen Sie Integrationszuverlässigkeit, Wiederverwendung, Incidents, Performance, Consumer-Ergebnisse und Verbesserungsbedarf.", - "cycle.station.consumer-producer-service-requirements": "Consumer, Producer & Service Requirements", + "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", "cycle.station.capability-architecture-platform-decisions": "Capability Architecture & Platform Decisions", "cycle.station.capability-solution-interaction-design": "Capability Solution & Interaction Design", "cycle.station.capability-delivery-operations": "Capability Delivery & Operations", "cycle.station.capability-readiness-assurance": "Capability Readiness Assurance", "cycle.station.capability-publishing-enablement": "Capability Publishing & Enablement", "cycle.station.capability-monitoring-improvement": "Capability Monitoring & Improvement", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Capability-Strategie: Führt die Definition wiederverwendbarer Fähigkeiten von Hypothese und Consumer-/Producer-Anforderungen über Architektur, Lösungsdesign, Lieferung, Readiness, Veröffentlichung und kontinuierliche Verbesserung.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Consumer, Producer & Service Requirements: Führt die Definition wiederverwendbarer Fähigkeiten von Hypothese und Consumer-/Producer-Anforderungen über Architektur, Lösungsdesign, Lieferung, Readiness, Veröffentlichung und kontinuierliche Verbesserung.", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Capability Architecture & Platform Decisions: Führt die Definition wiederverwendbarer Fähigkeiten von Hypothese und Consumer-/Producer-Anforderungen über Architektur, Lösungsdesign, Lieferung, Readiness, Veröffentlichung und kontinuierliche Verbesserung.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Capability Solution & Interaction Design: Führt die Definition wiederverwendbarer Fähigkeiten von Hypothese und Consumer-/Producer-Anforderungen über Architektur, Lösungsdesign, Lieferung, Readiness, Veröffentlichung und kontinuierliche Verbesserung.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Capability Delivery & Operations: Führt die Definition wiederverwendbarer Fähigkeiten von Hypothese und Consumer-/Producer-Anforderungen über Architektur, Lösungsdesign, Lieferung, Readiness, Veröffentlichung und kontinuierliche Verbesserung.", diff --git a/src/data/method/de/labels.resources.json b/src/data/method/de/labels.resources.json index 042735f..5d53b52 100644 --- a/src/data/method/de/labels.resources.json +++ b/src/data/method/de/labels.resources.json @@ -160,10 +160,10 @@ "resource.capacity-canvas.steps": "Current Business Volumes: Quantify current business volumes and transaction rates.", "resource.capacity-canvas.tips": "Use requirements canvases to capture what users need; use this canvas to quantify demand and inform scaling decisions.", "resource.customer-journey-canvas.title": "Customer Journey Canvas", - "resource.customer-journey-canvas.description": "Zeichnen Sie die Customer Journeys auf, um Bedürfnisse und Schmerzpunkte zu identifizieren und so das API-Design und die Benutzererfahrung zu verbessern.", - "resource.customer-journey-canvas.outcomes": "Verbessertes Kundenverständnis", - "resource.customer-journey-canvas.steps": "Kunden-Persona definieren", - "resource.customer-journey-canvas.tips": "Iterieren Sie mit dem Input des Teams, um die Schritte zu verfeinern", + "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", + "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", + "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", "resource.event-canvas.title": "Event Canvas", "resource.event-canvas.description": "Entwerfen Sie ereignisgesteuerte APIs, indem Sie Ereignisse, Auslöser und Verarbeitungslogik definieren.", "resource.event-canvas.outcomes": "Definierte ereignisgesteuerte Architektur", @@ -352,16 +352,16 @@ "resource.capacity-canvas.steps.4": "Skalierungsstrategien vorschlagen", "resource.capacity-canvas.tips.1": "Szenarien für Nutzungsspitzen definieren", "resource.capacity-canvas.tips.2": "Skalierbarkeitstests in die Planungsphase einbeziehen", - "resource.customer-journey-canvas.outcomes.1": "Verbessertes API-Design", - "resource.customer-journey-canvas.outcomes.2": "Bessere Nutzererfahrung", - "resource.customer-journey-canvas.steps.1": "Identifizieren Sie Auslöser für die Reise", - "resource.customer-journey-canvas.steps.2": "Beschreiben Sie das Ende der Reise", + "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", "resource.customer-journey-canvas.steps.3": "Abbildung von Fahrtschritten mit Ein- und Ausgängen", "resource.customer-journey-canvas.steps.4": "Kundenbedürfnisse identifizieren", "resource.customer-journey-canvas.steps.5": "Kundengewinne zusammenfassen", "resource.customer-journey-canvas.steps.6": "Definition der erforderlichen Inputs und der daraus resultierenden Outputs", "resource.customer-journey-canvas.steps.7": "Definieren Sie API-Interaktionen für jeden Schritt", - "resource.customer-journey-canvas.tips.1": "Verwenden Sie die Ergebnisse dieses Canvas als Grundlage für andere Canvas wie den API Value Proposition Canvas", + "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.event-canvas.outcomes.1": "Ereignisauslöser und Verarbeitungslogik löschen", "resource.event-canvas.outcomes.2": "Verbesserte Reaktionsfähigkeit auf Änderungen in Echtzeit", "resource.event-canvas.steps.1": "Definieren Sie Auslöser für jedes Ereignis", @@ -542,56 +542,46 @@ "resource.api-testing-best-practices.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.", "resource.apiops-CI-CD-for-apis.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.", "resource.api-audit-checklist.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.", - "resource.automation-opportunity-canvas.title": "Automation Hypothesis Canvas", - "resource.automation-opportunity-canvas.description": "A compact primary canvas for linking optional supporting evidence to a testable automation hypothesis and validation decision.", - "resource.automation-opportunity-canvas.outcomes": "Testable automation hypothesis", - "resource.automation-opportunity-canvas.outcomes.1": "Supporting evidence, scope, assumptions, and validation experiment linked without duplicating other canvases", - "resource.automation-opportunity-canvas.outcomes.2": "Evidence-based decision to proceed, revise, redesign the process, or reject", - "resource.automation-opportunity-canvas.steps": "State the automation hypothesis and reference Journey, Value Proposition, Domain, Business Impact, Capacity, or other evidence only where relevant.", - "resource.automation-opportunity-canvas.steps.1": "Define the automation scope, out-of-scope work, and initial implementation hypothesis without making an architecture decision.", - "resource.automation-opportunity-canvas.steps.2": "Identify critical assumptions, design the smallest useful validation experiment, and record the decision after reviewing evidence.", - "resource.automation-opportunity-canvas.tips": "Treat Customer Journey, Capability Value Proposition, Domain, Business Impact, and Capacity as optional supporting evidence, not required outputs for every automation opportunity.", - "resource.automation-opportunity-canvas.tips.1": "Stop, narrow, or redesign weak opportunities before implementation choices become locked.", - "resource.human-automation-responsibility-canvas.title": "Human-Automation Responsibility Canvas", - "resource.human-automation-responsibility-canvas.description": "A canvas for creating the initial allocation of what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "resource.human-automation-responsibility-canvas.outcomes": "Clear human and automation responsibilities", - "resource.human-automation-responsibility-canvas.outcomes.1": "Oversight, escalation, and audit evidence defined by process step", - "resource.human-automation-responsibility-canvas.outcomes.2": "Implementation mechanisms selected without assuming every step should be automated", - "resource.human-automation-responsibility-canvas.steps": "List the target process steps and current handoffs.", - "resource.human-automation-responsibility-canvas.steps.1": "Assign each step to people, rules, workflows, agents, systems, APIs, UI automation, or a hybrid responsibility.", - "resource.human-automation-responsibility-canvas.steps.2": "Define oversight, escalation, and evidence for each step so later architecture and workflow design can validate and refine the allocation.", - "resource.human-automation-responsibility-canvas.tips": "Keep accountability visible even when execution is automated.", - "resource.human-automation-responsibility-canvas.tips.1": "Revisit this canvas later only to validate architecture assumptions or refine workflow-level handoffs and exceptions.", + "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", + "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", + "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "A canvas for designing the automation sequence, states, data, triggers, decisions, system interactions, failure paths, evidence, monitoring, and recovery.", - "resource.automation-workflow-canvas.outcomes": "Testable automation workflow design", - "resource.automation-workflow-canvas.outcomes.1": "Triggers, stages, states, decisions, data, interactions, handoffs, exceptions, and recovery paths defined", - "resource.automation-workflow-canvas.outcomes.2": "Operational evidence and monitoring points identified before delivery", - "resource.automation-workflow-canvas.steps": "Separate the target process from the technical workflow.", - "resource.automation-workflow-canvas.steps.1": "Map triggers, inputs, stages, states, decisions, automation actions, system interactions, data sources, handoffs, outputs, and exceptions.", - "resource.automation-workflow-canvas.steps.2": "Define retries, timeouts, duplicate prevention, audit evidence, monitoring points, and recovery paths.", - "resource.automation-workflow-canvas.tips": "Treat exceptions and manual recovery as part of the design, not an afterthought.", - "resource.automation-workflow-canvas.tips.1": "Revisit the Human-Automation Responsibility Canvas separately to refine responsibility allocation, oversight, escalation, and evidence for the workflow stages now being designed.", + "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", + "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", + "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "A canvas for comparing and justifying alternative implementation mechanisms for an automation solution.", - "resource.automation-architecture-decision-canvas.outcomes": "Justified automation architecture and implementation approach", - "resource.automation-architecture-decision-canvas.outcomes.1": "Candidate mechanisms compared on quality, risk, cost, skills, and operational fit", - "resource.automation-architecture-decision-canvas.outcomes.2": "Hybrid solution decisions documented", - "resource.automation-architecture-decision-canvas.steps": "Markieren Sie jeden Kandidatenmechanismus als betrachtet, ausgewählt, abgelehnt oder nicht relevant, bevor Sie die tragfähigen Optionen vergleichen.", - "resource.automation-architecture-decision-canvas.steps.1": "Evaluate feasibility, reliability, security, maintainability, latency, scalability, cost, vendor dependency, testability, observability, recoverability, skills, and architectural fit.", - "resource.automation-architecture-decision-canvas.steps.2": "Document the preferred hybrid approach, rationale, risks, and open assumptions.", - "resource.automation-architecture-decision-canvas.tips": "Do not force every mechanism into the solution; make irrelevant candidates explicit and compare only viable options.", - "resource.automation-architecture-decision-canvas.tips.1": "Choose UI automation only when more stable system or integration paths are insufficient.", + "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", + "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", + "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", - "resource.automation-readiness-operations-canvas.description": "A canvas for preparing the operating model for a safely released, supported, monitored, and recoverable automation.", - "resource.automation-readiness-operations-canvas.outcomes": "Documented automation operating model", - "resource.automation-readiness-operations-canvas.outcomes.1": "Ownership, permissions, environments, evidence, monitoring, support, fallback, rollback, and risks prepared", - "resource.automation-readiness-operations-canvas.outcomes.2": "Release readiness status and improvement backlog ready for readiness review and post-release learning", - "resource.automation-readiness-operations-canvas.steps": "Prepare business owner, operational owner, affected users, permissions, credentials, environments, and documentation.", - "resource.automation-readiness-operations-canvas.steps.1": "Prepare test evidence, exception handling, monitoring, support, manual fallback, rollback, and known risks.", - "resource.automation-readiness-operations-canvas.steps.2": "Dokumentieren Sie den Release-Readiness-Status und den Verbesserungs-Backlog, ohne die formale Readiness-Entscheidung zu treffen.", - "resource.automation-readiness-operations-canvas.tips": "Nutzen Sie dies während Delivery & Operations, um Nachweise vorzubereiten; nutzen Sie die Automatisierungs-Readiness-Checkliste für die formale Freigabeentscheidung.", - "resource.automation-readiness-operations-canvas.tips.1": "Make manual fallback and operational ownership explicit before production use.", + "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", + "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", + "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", @@ -613,46 +603,46 @@ "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", "resource.automation-monitoring-value-metrics.tips": "Monitoring verwandelt operative, Nutzer-, Risiko- und Wertnachweise in Lifecycle-Entscheidungen und einen Verbesserungs-Backlog.", "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Hypothesis Canvas", - "resource.integration-capability-hypothesis-canvas.description": "Integration Capability Hypothesis Canvas unterstützt die Planung, Entscheidung, Lieferung, Veröffentlichung oder Verbesserung einer wiederverwendbaren Integrationsfähigkeit.", - "resource.integration-capability-hypothesis-canvas.outcomes": "Dokumentierte Integrationsgrundlage", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Wichtige Entscheidungen, Verantwortlichkeiten, Nachweise und Randbedingungen festgehalten", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "Nächste Schritte, Risiken und offene Punkte für die Integrationsarbeit sichtbar", - "resource.integration-capability-hypothesis-canvas.steps": "Klären Sie Zweck, Beteiligte, Umfang und relevante Nachweise.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Bedingungen, Verantwortlichkeiten und benötigte Artefakte.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Nutzen Sie die Ergebnisse für Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.integration-capability-hypothesis-canvas.tips": "Passen Sie diese Ressource an den gewählten Integrationsstil an.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Beziehen Sie Producer, Consumer, Plattform, Betrieb, Security, Compliance und Business ein.", - "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Requirements Canvas", - "resource.integration-consumer-provider-requirements-canvas.description": "Integration Consumer & Provider Requirements Canvas unterstützt die Planung, Entscheidung, Lieferung, Veröffentlichung oder Verbesserung einer wiederverwendbaren Integrationsfähigkeit.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "Dokumentierte Integrationsgrundlage", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Wichtige Entscheidungen, Verantwortlichkeiten, Nachweise und Randbedingungen festgehalten", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "Nächste Schritte, Risiken und offene Punkte für die Integrationsarbeit sichtbar", - "resource.integration-consumer-provider-requirements-canvas.steps": "Klären Sie Zweck, Beteiligte, Umfang und relevante Nachweise.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Bedingungen, Verantwortlichkeiten und benötigte Artefakte.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Nutzen Sie die Ergebnisse für Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Passen Sie diese Ressource an den gewählten Integrationsstil an.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Beziehen Sie Producer, Consumer, Plattform, Betrieb, Security, Compliance und Business ein.", + "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", + "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", + "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", + "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", - "resource.integration-architecture-decision-canvas.description": "Integration Architecture Decision Canvas unterstützt die Planung, Entscheidung, Lieferung, Veröffentlichung oder Verbesserung einer wiederverwendbaren Integrationsfähigkeit.", - "resource.integration-architecture-decision-canvas.outcomes": "Dokumentierte Integrationsgrundlage", - "resource.integration-architecture-decision-canvas.outcomes.1": "Kandidatenstile mit Status verglichen und ausgewählter Stil oder Hybrid festgehalten", - "resource.integration-architecture-decision-canvas.outcomes.2": "Nächste Schritte, Risiken und offene Punkte für die Integrationsarbeit sichtbar", - "resource.integration-architecture-decision-canvas.steps": "Nutzen Sie die Kandidatenstatus-Auswahl, um jeden Stil als betrachtet, ausgewählt, abgelehnt oder nicht relevant zu markieren.", - "resource.integration-architecture-decision-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Bedingungen, Verantwortlichkeiten und benötigte Artefakte.", - "resource.integration-architecture-decision-canvas.steps.2": "Nutzen Sie die Ergebnisse für Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.integration-architecture-decision-canvas.tips": "Passen Sie diese Ressource an den gewählten Integrationsstil an.", - "resource.integration-architecture-decision-canvas.tips.1": "Beziehen Sie Producer, Consumer, Plattform, Betrieb, Security, Compliance und Business ein.", + "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", + "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", + "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", - "resource.integration-readiness-operations-canvas.description": "Integration Readiness & Operations Canvas unterstützt die Planung, Entscheidung, Lieferung, Veröffentlichung oder Verbesserung einer wiederverwendbaren Integrationsfähigkeit.", - "resource.integration-readiness-operations-canvas.outcomes": "Dokumentierte Integrationsgrundlage", - "resource.integration-readiness-operations-canvas.outcomes.1": "Wichtige Entscheidungen, Verantwortlichkeiten, Nachweise und Randbedingungen festgehalten", - "resource.integration-readiness-operations-canvas.outcomes.2": "Nächste Schritte, Risiken und offene Punkte für die Integrationsarbeit sichtbar", - "resource.integration-readiness-operations-canvas.steps": "Klären Sie Zweck, Beteiligte, Umfang und relevante Nachweise.", - "resource.integration-readiness-operations-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Bedingungen, Verantwortlichkeiten und benötigte Artefakte.", - "resource.integration-readiness-operations-canvas.steps.2": "Nutzen Sie die Ergebnisse für Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.integration-readiness-operations-canvas.tips": "Passen Sie diese Ressource an den gewählten Integrationsstil an.", - "resource.integration-readiness-operations-canvas.tips.1": "Beziehen Sie Producer, Consumer, Plattform, Betrieb, Security, Compliance und Business ein.", + "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", + "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", + "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-consumer-onboarding-guide.title": "Leitfaden für Integrations-Consumer-Onboarding", "resource.integration-consumer-onboarding-guide.description": "Leitfaden für Integrations-Consumer-Onboarding unterstützt die Planung, Entscheidung, Lieferung, Veröffentlichung oder Verbesserung einer wiederverwendbaren Integrationsfähigkeit.", "resource.integration-consumer-onboarding-guide.outcomes": "Dokumentierte Integrationsgrundlage", @@ -824,65 +814,65 @@ "resource.integration-lifecycle-management-guide.tips": "Passen Sie diese Ressource an den gewählten Integrationsstil an.", "resource.integration-lifecycle-management-guide.tips.1": "Beziehen Sie Producer, Consumer, Plattform, Betrieb, Security, Compliance und Business ein.", "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", - "resource.integration-solution-design-canvas.description": "Ein Summary-Canvas für Integrationsdesign-Entscheidungen über Stile hinweg, einschließlich Stil, Producer, Consumer, Verträge, Schemas, Mappings, Liefermuster, Security, Fehlerbehandlung, Retry, Replay, Korrelation, Abstimmung, Beobachtbarkeit und Versionierung.", - "resource.integration-solution-design-canvas.outcomes": "Vollständige Zusammenfassung des Integrationsdesigns", - "resource.integration-solution-design-canvas.outcomes.1": "Vertrags-, Schema-, Mapping-, Liefer-, Security-, Recovery- und Observability-Entscheidungen dokumentiert", - "resource.integration-solution-design-canvas.outcomes.2": "Design auf Architekturentscheidung und Consumer-/Provider-Anforderungen zurückführbar", - "resource.integration-solution-design-canvas.steps": "Beginnen Sie mit dem ausgewählten Architekturstil oder Hybrid.", - "resource.integration-solution-design-canvas.steps.1": "Dokumentieren Sie Verträge, Schemas, Mappings, Transformationen, Liefermuster, Identität, Security, Fehler, Retry, Replay, Korrelation, Abstimmung, Beobachtbarkeit und Versionierung.", - "resource.integration-solution-design-canvas.steps.2": "Nutzen Sie Interaction Canvas und stilspezifische Ressourcen nur dort, wo tieferes Designdetail benötigt wird.", - "resource.integration-solution-design-canvas.tips": "Nutzen Sie dies als primäres Artefakt für Integration Solution Design.", - "resource.integration-solution-design-canvas.tips.1": "Berücksichtigen Sie Workflow-Orchestrierung, B2B/EDI, Webhooks, kanonische Datenmodelle, Dateien, Streams, Messaging, Datenprodukte, APIs und Connectors dort, wo sie relevant sind.", - "resource.capability-hypothesis-canvas.title": "Capability Hypothesis Canvas", - "resource.capability-hypothesis-canvas.description": "Capability Hypothesis Canvas unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", - "resource.capability-hypothesis-canvas.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "resource.capability-hypothesis-canvas.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "resource.capability-hypothesis-canvas.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "resource.capability-hypothesis-canvas.steps": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "resource.capability-hypothesis-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "resource.capability-hypothesis-canvas.steps.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.capability-hypothesis-canvas.tips": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "resource.capability-hypothesis-canvas.tips.1": "Behandeln Sie unterstützende Canvases als optionale Nachweise, nicht als Pflichtarbeit.", - "resource.capability-consumer-producer-requirements-canvas.title": "Consumer & Producer Requirements Canvas", - "resource.capability-consumer-producer-requirements-canvas.description": "Consumer & Producer Requirements Canvas unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "resource.capability-consumer-producer-requirements-canvas.steps": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Behandeln Sie unterstützende Canvases als optionale Nachweise, nicht als Pflichtarbeit.", + "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", + "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", + "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", + "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", + "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", + "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", + "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", - "resource.capability-architecture-decision-canvas.description": "Capability Architecture Decision Canvas unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", - "resource.capability-architecture-decision-canvas.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "resource.capability-architecture-decision-canvas.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "resource.capability-architecture-decision-canvas.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "resource.capability-architecture-decision-canvas.steps": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "resource.capability-architecture-decision-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "resource.capability-architecture-decision-canvas.steps.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.capability-architecture-decision-canvas.tips": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "resource.capability-architecture-decision-canvas.tips.1": "Behandeln Sie unterstützende Canvases als optionale Nachweise, nicht als Pflichtarbeit.", + "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", + "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", + "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", - "resource.capability-solution-design-canvas.description": "Capability Solution Design Canvas unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", - "resource.capability-solution-design-canvas.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "resource.capability-solution-design-canvas.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "resource.capability-solution-design-canvas.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "resource.capability-solution-design-canvas.steps": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "resource.capability-solution-design-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "resource.capability-solution-design-canvas.steps.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.capability-solution-design-canvas.tips": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "resource.capability-solution-design-canvas.tips.1": "Behandeln Sie unterstützende Canvases als optionale Nachweise, nicht als Pflichtarbeit.", + "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", + "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", + "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", - "resource.capability-readiness-operations-canvas.description": "Capability Readiness & Operations Canvas unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", - "resource.capability-readiness-operations-canvas.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "resource.capability-readiness-operations-canvas.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "resource.capability-readiness-operations-canvas.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "resource.capability-readiness-operations-canvas.steps": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "resource.capability-readiness-operations-canvas.steps.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "resource.capability-readiness-operations-canvas.steps.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "resource.capability-readiness-operations-canvas.tips": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "resource.capability-readiness-operations-canvas.tips.1": "Behandeln Sie unterstützende Canvases als optionale Nachweise, nicht als Pflichtarbeit.", + "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", + "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", + "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-consumer-onboarding-guide.title": "Leitfaden für Capability Consumer Onboarding", "resource.capability-consumer-onboarding-guide.description": "Leitfaden für Capability Consumer Onboarding unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", "resource.capability-consumer-onboarding-guide.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", diff --git a/src/data/method/en/labels.cycles.json b/src/data/method/en/labels.cycles.json index 19aeaa8..e39d6d8 100644 --- a/src/data/method/en/labels.cycles.json +++ b/src/data/method/en/labels.cycles.json @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "API Publishing", "cycle.station.monitoring-and-improving": "API Monitoring & Improvement", "cycle.station.integration-capability-strategy": "Integration Capability Strategy", - "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer Requirements & Onboarding", + "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", "cycle.station.integration-architecture-decision": "Integration Architecture & Platform Decisions", "cycle.station.integration-solution-design": "Integration Solution Design", "cycle.station.integration-delivery-operations": "Integration Delivery & Operations", @@ -47,7 +47,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitor API health, adoption, consumer outcomes, reliability, and improvement opportunities after release.", "cycle.automation-cycle.title": "Automation Cycle", "cycle.automation-cycle.description": "A cycle for selecting, designing, delivering, enabling, and improving automation solutions across people, rules, workflows, agents, integrations, UI automation, and operations.", - "cycle.automation-cycle.purpose": "Guide teams from a validated automation opportunity to a governed, operable automation solution by deciding what each step should be performed by: a person, rule, workflow, agent, API or system integration, connector, custom code, or UI automation.", + "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", "cycle.audience.automation-owners": "Automation owners", "cycle.audience.process-owners": "Process owners", "cycle.audience.automation-teams": "Automation teams", @@ -57,33 +57,33 @@ "cycle.station.automation-readiness-review": "Automation Readiness Review", "cycle.station.automation-enablement": "Automation Rollout & Enablement", "cycle.station.automation-monitoring-improvement": "Automation Monitoring & Improvement", - "cycle.automation-cycle.station.api-product-strategy.description": "Prioritize a testable automation hypothesis. Use Customer Journey, Capability Value Proposition, Domain, Business Impact, Capacity, or other canvases only as optional supporting evidence where relevant.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Create the initial human-automation responsibility allocation and capture user, operator, permission, activation, support, recovery, observability, and non-functional requirements before implementation choices are made.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Evaluate and justify the automation architecture and implementation approach against requirements, responsibility assumptions, feasibility, security, reliability, operability, cost, and risk.", - "cycle.automation-cycle.station.api-design.description": "Design the automation workflow sequence, states, triggers, data, decisions, system interactions, handoffs, exceptions, evidence, monitoring points, and recovery paths.", + "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", + "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", "cycle.automation-cycle.station.api-audit.description": "Use a readiness checklist to review evidence and record the release decision: ready, ready with conditions, remediation required, or not approved.", "cycle.automation-cycle.station.api-publishing.description": "Activate and roll out the automation safely with communications, training, operating instructions, support paths, adoption monitoring, feedback channels, phased rollout, pause, and rollback conditions.", "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process, User & Automation Requirements", + "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Prioritize a reusable integration capability hypothesis by linking consumer, value, domain, ownership, reuse, and viability evidence to a clear scope, assumptions, validation step, and proceed-or-stop decision.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Capture integration consumers, provider responsibilities, onboarding needs, service expectations, and operational constraints.", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Select the integration architecture, implementation style, and platform capabilities, taking account of constraints and the governance model.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Design the integration solution, contracts, schemas, data structures, mappings, and interaction or delivery patterns for the selected style.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Build, test, deploy, and operate the integration capability using its selected implementation style and validated contract.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Publish the integration capability so teams can discover it, evaluate it, request access, complete onboarding, reuse it, and get support.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.", - "cycle.station.consumer-producer-service-requirements": "Consumer, Producer & Service Requirements", + "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", "cycle.station.capability-architecture-platform-decisions": "Capability Architecture & Platform Decisions", "cycle.station.capability-solution-interaction-design": "Capability Solution & Interaction Design", "cycle.station.capability-delivery-operations": "Capability Delivery & Operations", "cycle.station.capability-readiness-assurance": "Capability Readiness Assurance", "cycle.station.capability-publishing-enablement": "Capability Publishing & Enablement", "cycle.station.capability-monitoring-improvement": "Capability Monitoring & Improvement", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Prioritize a reusable digital capability hypothesis by linking consumer, value, domain, ownership, viability, and reuse evidence to a clear scope, assumptions, validation step, and decision. Use supporting canvases only where the necessary evidence does not already exist.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Capture intended consumers, consuming contexts, capability owner and producer responsibilities, discovery, access, service, quality, support, lifecycle, operational, and governance requirements.", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Select the capability implementation style, architecture pattern, enabling platform, and governance model from evidence.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Design how consumers access, interact with, receive, or use the capability through the selected implementation style.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Deliver and operate the reusable capability using implementation-style-appropriate engineering, testing, security, release, support, and operational ownership practices.", diff --git a/src/data/method/en/labels.resources.json b/src/data/method/en/labels.resources.json index 163a5ba..bdb0d2e 100644 --- a/src/data/method/en/labels.resources.json +++ b/src/data/method/en/labels.resources.json @@ -323,20 +323,20 @@ "resource.capacity-canvas.tips.1": "Use measured data where available and state assumptions explicitly.", "resource.capacity-canvas.tips.2": "Revisit the canvas after pilots or material changes in demand.", "resource.customer-journey-canvas.title": "Customer Journey Canvas", - "resource.customer-journey-canvas.description": "Map customer, partner, or consumer journeys to identify needs, pain points, gains, inputs, outputs, and experience expectations.", - "resource.customer-journey-canvas.outcomes": "Shared understanding of the customer, partner, or consumer journey", - "resource.customer-journey-canvas.outcomes.1": "Needs, pain points, gains, inputs, and outputs documented", - "resource.customer-journey-canvas.outcomes.2": "Journey evidence available for capability, requirements, and architecture decisions", - "resource.customer-journey-canvas.steps": "Define customer persona", - "resource.customer-journey-canvas.steps.1": "Identify triggers for the journey", - "resource.customer-journey-canvas.steps.2": "Describe the journey's end", + "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", + "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", + "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", "resource.customer-journey-canvas.steps.3": "Map journey steps with inputs/outputs", "resource.customer-journey-canvas.steps.4": "Identify customer pains", "resource.customer-journey-canvas.steps.5": "Summarize customer gains", "resource.customer-journey-canvas.steps.6": "Define necessary inputs and resulting outputs", "resource.customer-journey-canvas.steps.7": "Define interactions and processing expectations for each step", - "resource.customer-journey-canvas.tips": "Validate the journey with people who perform or experience it.", - "resource.customer-journey-canvas.tips.1": "Use the results to inform value proposition, domain, requirements, and architecture work.", + "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.event-canvas.title": "Event Canvas", "resource.event-canvas.description": "Design event-driven interfaces and integrations by defining events, triggers, schemas, producers, consumers, and processing logic.", "resource.event-canvas.outcomes": "Defined event-driven interaction model", @@ -542,56 +542,46 @@ "resource.api-testing-best-practices.tips.2": "Use this resource when an API is the selected implementation style.", "resource.apiops-CI-CD-for-apis.tips.2": "Use this resource when an API is the selected implementation style.", "resource.api-audit-checklist.tips.2": "Use this resource when an API is the selected implementation style.", - "resource.automation-opportunity-canvas.title": "Automation Hypothesis Canvas", - "resource.automation-opportunity-canvas.description": "A compact primary canvas for linking optional supporting evidence to a testable automation hypothesis and validation decision.", - "resource.automation-opportunity-canvas.outcomes": "Testable automation hypothesis", - "resource.automation-opportunity-canvas.outcomes.1": "Supporting evidence, scope, assumptions, and validation experiment linked without duplicating other canvases", - "resource.automation-opportunity-canvas.outcomes.2": "Evidence-based decision to proceed, revise, redesign the process, or reject", - "resource.automation-opportunity-canvas.steps": "State the automation hypothesis and reference Journey, Value Proposition, Domain, Business Impact, Capacity, or other evidence only where relevant.", - "resource.automation-opportunity-canvas.steps.1": "Define the automation scope, out-of-scope work, and initial implementation hypothesis without making an architecture decision.", - "resource.automation-opportunity-canvas.steps.2": "Identify critical assumptions, design the smallest useful validation experiment, and record the decision after reviewing evidence.", - "resource.automation-opportunity-canvas.tips": "Treat Customer Journey, Capability Value Proposition, Domain, Business Impact, and Capacity as optional supporting evidence, not required outputs for every automation opportunity.", - "resource.automation-opportunity-canvas.tips.1": "Stop, narrow, or redesign weak opportunities before implementation choices become locked.", - "resource.human-automation-responsibility-canvas.title": "Human-Automation Responsibility Canvas", - "resource.human-automation-responsibility-canvas.description": "A canvas for creating the initial allocation of what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "resource.human-automation-responsibility-canvas.outcomes": "Clear human and automation responsibilities", - "resource.human-automation-responsibility-canvas.outcomes.1": "Oversight, escalation, and audit evidence defined by process step", - "resource.human-automation-responsibility-canvas.outcomes.2": "Implementation mechanisms selected without assuming every step should be automated", - "resource.human-automation-responsibility-canvas.steps": "List the target process steps and current handoffs.", - "resource.human-automation-responsibility-canvas.steps.1": "Assign each step to people, rules, workflows, agents, systems, APIs, UI automation, or a hybrid responsibility.", - "resource.human-automation-responsibility-canvas.steps.2": "Define oversight, escalation, and evidence for each step so later architecture and workflow design can validate and refine the allocation.", - "resource.human-automation-responsibility-canvas.tips": "Keep accountability visible even when execution is automated.", - "resource.human-automation-responsibility-canvas.tips.1": "Revisit this canvas later only to validate architecture assumptions or refine workflow-level handoffs and exceptions.", + "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", + "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", + "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "A canvas for designing the automation sequence, states, data, triggers, decisions, system interactions, failure paths, evidence, monitoring, and recovery.", - "resource.automation-workflow-canvas.outcomes": "Testable automation workflow design", - "resource.automation-workflow-canvas.outcomes.1": "Triggers, stages, states, decisions, data, interactions, handoffs, exceptions, and recovery paths defined", - "resource.automation-workflow-canvas.outcomes.2": "Operational evidence and monitoring points identified before delivery", - "resource.automation-workflow-canvas.steps": "Separate the target process from the technical workflow.", - "resource.automation-workflow-canvas.steps.1": "Map triggers, inputs, stages, states, decisions, automation actions, system interactions, data sources, handoffs, outputs, and exceptions.", - "resource.automation-workflow-canvas.steps.2": "Define retries, timeouts, duplicate prevention, audit evidence, monitoring points, and recovery paths.", - "resource.automation-workflow-canvas.tips": "Treat exceptions and manual recovery as part of the design, not an afterthought.", - "resource.automation-workflow-canvas.tips.1": "Revisit the Human-Automation Responsibility Canvas separately to refine responsibility allocation, oversight, escalation, and evidence for the workflow stages now being designed.", + "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", + "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", + "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "A canvas for comparing and justifying alternative implementation mechanisms for an automation solution.", - "resource.automation-architecture-decision-canvas.outcomes": "Justified automation architecture and implementation approach", - "resource.automation-architecture-decision-canvas.outcomes.1": "Candidate mechanisms compared on quality, risk, cost, skills, and operational fit", - "resource.automation-architecture-decision-canvas.outcomes.2": "Hybrid solution decisions documented", - "resource.automation-architecture-decision-canvas.steps": "Mark each candidate mechanism as considered, selected, rejected, or not relevant before comparing the viable options.", - "resource.automation-architecture-decision-canvas.steps.1": "Evaluate feasibility, reliability, security, maintainability, latency, scalability, cost, vendor dependency, testability, observability, recoverability, skills, and architectural fit.", - "resource.automation-architecture-decision-canvas.steps.2": "Document the preferred hybrid approach, rationale, risks, and open assumptions.", - "resource.automation-architecture-decision-canvas.tips": "Do not force every mechanism into the solution; make irrelevant candidates explicit and compare only viable options.", - "resource.automation-architecture-decision-canvas.tips.1": "Choose UI automation only when more stable system or integration paths are insufficient.", + "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", + "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", + "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", - "resource.automation-readiness-operations-canvas.description": "A canvas for preparing the operating model for a safely released, supported, monitored, and recoverable automation.", - "resource.automation-readiness-operations-canvas.outcomes": "Documented automation operating model", - "resource.automation-readiness-operations-canvas.outcomes.1": "Ownership, permissions, environments, evidence, monitoring, support, fallback, rollback, and risks prepared", - "resource.automation-readiness-operations-canvas.outcomes.2": "Release readiness status and improvement backlog ready for readiness review and post-release learning", - "resource.automation-readiness-operations-canvas.steps": "Prepare business owner, operational owner, affected users, permissions, credentials, environments, and documentation.", - "resource.automation-readiness-operations-canvas.steps.1": "Prepare test evidence, exception handling, monitoring, support, manual fallback, rollback, and known risks.", - "resource.automation-readiness-operations-canvas.steps.2": "Record release readiness status and the improvement backlog without making the formal readiness decision.", - "resource.automation-readiness-operations-canvas.tips": "Use this during Delivery & Operations to prepare evidence; use the Automation Readiness Checklist for the formal release decision.", - "resource.automation-readiness-operations-canvas.tips.1": "Make manual fallback and operational ownership explicit before production use.", + "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", + "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", + "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", @@ -613,46 +603,46 @@ "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", "resource.automation-monitoring-value-metrics.tips": "Monitoring turns operational, user, risk, and value evidence into lifecycle decisions and an improvement backlog.", "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Hypothesis Canvas", - "resource.integration-capability-hypothesis-canvas.description": "A compact canvas for turning optional journey, value, domain, ownership, reuse, and viability evidence into a testable integration capability hypothesis.", - "resource.integration-capability-hypothesis-canvas.outcomes": "Testable integration capability hypothesis", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Scope, consumers, owner, evidence, assumptions, validation, and decision documented", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "Optional supporting canvases referenced without making them mandatory", - "resource.integration-capability-hypothesis-canvas.steps": "State the integration capability hypothesis and reuse scope.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Link supporting evidence from existing canvases or research.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Record assumptions, validation experiment, and proceed-or-stop decision.", - "resource.integration-capability-hypothesis-canvas.tips": "Use this as the primary strategy artifact.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Keep Customer Journey, Domain, Capability Value Proposition, and Capability Business Model canvases as optional evidence.", - "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Requirements Canvas", - "resource.integration-consumer-provider-requirements-canvas.description": "A canvas for consumer systems, provider responsibilities, onboarding, access, service expectations, observability, support, failure handling, replay, reconciliation, and recovery requirements.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "Integration consumer and provider requirements", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Consumer, provider, access, environment, and support expectations clarified", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "Architecture-relevant constraints ready for decision making", - "resource.integration-consumer-provider-requirements-canvas.steps": "Identify consumer systems, teams, and provider responsibilities.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Capture onboarding, access, credentials, environments, compatibility, and service expectations.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Record data quality, observability, support, failure handling, replay, reconciliation, and recovery requirements.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Use before architecture selection.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Keep API onboarding guidance conditional for API-based implementations.", + "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", + "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", + "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", + "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", - "resource.integration-architecture-decision-canvas.description": "A canvas for comparing integration styles and recording selected architecture, platform decision, rationale, rejected alternatives, risks, and assumptions.", - "resource.integration-architecture-decision-canvas.outcomes": "Justified integration architecture decision", - "resource.integration-architecture-decision-canvas.outcomes.1": "Candidate styles compared with status, and selected style or hybrid recorded", - "resource.integration-architecture-decision-canvas.outcomes.2": "Rejected alternatives, platform decision, risks, and assumptions documented", - "resource.integration-architecture-decision-canvas.steps": "Use the candidate status control to mark each style as considered, selected, rejected, or not relevant.", - "resource.integration-architecture-decision-canvas.steps.1": "Compare viable options against timing, coupling, ownership, reliability, data quality, security, operability, cost, governance, platform fit, and skills.", - "resource.integration-architecture-decision-canvas.steps.2": "Record the selected style, platform decision, rationale, rejected alternatives, risks, and assumptions.", - "resource.integration-architecture-decision-canvas.tips": "Use Business Impact, Location, and Capacity as conditional inputs.", - "resource.integration-architecture-decision-canvas.tips.1": "Do not treat API, event, file, stream, or data product as mandatory candidates.", + "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", + "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", + "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", - "resource.integration-readiness-operations-canvas.description": "A canvas for preparing ownership, environments, credentials, deployment, monitoring, support, retry, replay, reconciliation, fallback, rollback, incidents, evidence, risks, and readiness status.", - "resource.integration-readiness-operations-canvas.outcomes": "Integration operating model prepared", - "resource.integration-readiness-operations-canvas.outcomes.1": "Business, integration, producer, consumer, platform, and operational ownership clarified", - "resource.integration-readiness-operations-canvas.outcomes.2": "Evidence, risks, support, recovery, and readiness status prepared before release review", - "resource.integration-readiness-operations-canvas.steps": "Record business, integration, producer, consumer, platform, and operational owners.", - "resource.integration-readiness-operations-canvas.steps.1": "Prepare environments, credentials, deployment, monitoring, support, retry, replay, reconciliation, fallback, rollback, and incident ownership.", - "resource.integration-readiness-operations-canvas.steps.2": "Record test evidence, known risks, conditions, remediation, and readiness status.", - "resource.integration-readiness-operations-canvas.tips": "Use this during delivery and operations.", - "resource.integration-readiness-operations-canvas.tips.1": "Use the Integration Readiness Checklist for the formal release decision.", + "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", + "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", + "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-consumer-onboarding-guide.title": "Integration Consumer Onboarding Guide", "resource.integration-consumer-onboarding-guide.description": "Guidance for helping consumer teams discover, request access to, test, validate, and start using an integration capability.", "resource.integration-consumer-onboarding-guide.outcomes": "Consumer onboarding path", @@ -824,65 +814,65 @@ "resource.integration-lifecycle-management-guide.tips": "Use during periodic monitoring and portfolio review.", "resource.integration-lifecycle-management-guide.tips.1": "Treat unmanaged point-to-point growth as lifecycle evidence.", "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", - "resource.integration-solution-design-canvas.description": "A summary canvas for cross-style integration design decisions, including selected style, producers, consumers, contracts, schemas, mappings, delivery pattern, security, error handling, retry, replay, correlation, reconciliation, observability, and versioning.", - "resource.integration-solution-design-canvas.outcomes": "Complete integration solution design summary", - "resource.integration-solution-design-canvas.outcomes.1": "Contract, schema, mapping, delivery, security, recovery, and observability decisions documented", - "resource.integration-solution-design-canvas.outcomes.2": "Design traceable to architecture decision and consumer/provider requirements", - "resource.integration-solution-design-canvas.steps": "Start from the selected architecture style or hybrid.", - "resource.integration-solution-design-canvas.steps.1": "Document contracts, schemas, mappings, transformations, delivery pattern, identity, security, errors, retry, replay, correlation, reconciliation, observability, and versioning.", - "resource.integration-solution-design-canvas.steps.2": "Use Interaction Canvas and style-specific resources only where deeper design detail is needed.", - "resource.integration-solution-design-canvas.tips": "Use this as the primary Integration Solution Design artifact.", - "resource.integration-solution-design-canvas.tips.1": "Cover workflow orchestration, B2B/EDI, webhooks, canonical data models, files, streams, messaging, data products, APIs, and connectors where relevant.", - "resource.capability-hypothesis-canvas.title": "Capability Hypothesis Canvas", - "resource.capability-hypothesis-canvas.description": "A compact canvas for linking consumer, value, domain, ownership, viability, and reuse evidence to a testable capability hypothesis and decision.", - "resource.capability-hypothesis-canvas.outcomes": "Documented capability decision or working artifact", - "resource.capability-hypothesis-canvas.outcomes.1": "Consumer, producer, owner, evidence, constraints, and service expectations clarified", - "resource.capability-hypothesis-canvas.outcomes.2": "Risks, assumptions, next steps, and lifecycle implications visible", - "resource.capability-hypothesis-canvas.steps": "Clarify the capability purpose, consumers, producers, scope, and evidence.", - "resource.capability-hypothesis-canvas.steps.1": "Document decisions, responsibilities, service expectations, risks, and required artifacts.", - "resource.capability-hypothesis-canvas.steps.2": "Use the output for architecture, design, delivery, readiness, publishing, or improvement.", - "resource.capability-hypothesis-canvas.tips": "Use style-specific API, integration, workflow, data product, or application guidance only after the implementation style is selected.", - "resource.capability-hypothesis-canvas.tips.1": "Keep supporting canvases optional evidence rather than mandatory work.", - "resource.capability-consumer-producer-requirements-canvas.title": "Consumer & Producer Requirements Canvas", - "resource.capability-consumer-producer-requirements-canvas.description": "A canvas for capturing mutual consumer and producer requirements, service expectations, governance constraints, support, change, lifecycle, and architecture implications.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "Documented capability decision or working artifact", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Consumer, producer, owner, evidence, constraints, and service expectations clarified", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "Risks, assumptions, next steps, and lifecycle implications visible", - "resource.capability-consumer-producer-requirements-canvas.steps": "Clarify the capability purpose, consumers, producers, scope, and evidence.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Document decisions, responsibilities, service expectations, risks, and required artifacts.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Use the output for architecture, design, delivery, readiness, publishing, or improvement.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Use style-specific API, integration, workflow, data product, or application guidance only after the implementation style is selected.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Keep supporting canvases optional evidence rather than mandatory work.", + "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", + "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", + "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", + "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", + "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", + "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", + "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", - "resource.capability-architecture-decision-canvas.description": "A decision canvas for comparing implementation styles and recording selected style, platform, rationale, rejected alternatives, assumptions, and risks.", - "resource.capability-architecture-decision-canvas.outcomes": "Documented capability decision or working artifact", - "resource.capability-architecture-decision-canvas.outcomes.1": "Consumer, producer, owner, evidence, constraints, and service expectations clarified", - "resource.capability-architecture-decision-canvas.outcomes.2": "Risks, assumptions, next steps, and lifecycle implications visible", - "resource.capability-architecture-decision-canvas.steps": "Clarify the capability purpose, consumers, producers, scope, and evidence.", - "resource.capability-architecture-decision-canvas.steps.1": "Document decisions, responsibilities, service expectations, risks, and required artifacts.", - "resource.capability-architecture-decision-canvas.steps.2": "Use the output for architecture, design, delivery, readiness, publishing, or improvement.", - "resource.capability-architecture-decision-canvas.tips": "Use style-specific API, integration, workflow, data product, or application guidance only after the implementation style is selected.", - "resource.capability-architecture-decision-canvas.tips.1": "Keep supporting canvases optional evidence rather than mandatory work.", + "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", + "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", + "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", - "resource.capability-solution-design-canvas.description": "A canvas for designing how consumers access, interact with, receive, or use a reusable capability through the selected implementation style.", - "resource.capability-solution-design-canvas.outcomes": "Documented capability decision or working artifact", - "resource.capability-solution-design-canvas.outcomes.1": "Consumer, producer, owner, evidence, constraints, and service expectations clarified", - "resource.capability-solution-design-canvas.outcomes.2": "Risks, assumptions, next steps, and lifecycle implications visible", - "resource.capability-solution-design-canvas.steps": "Clarify the capability purpose, consumers, producers, scope, and evidence.", - "resource.capability-solution-design-canvas.steps.1": "Document decisions, responsibilities, service expectations, risks, and required artifacts.", - "resource.capability-solution-design-canvas.steps.2": "Use the output for architecture, design, delivery, readiness, publishing, or improvement.", - "resource.capability-solution-design-canvas.tips": "Use style-specific API, integration, workflow, data product, or application guidance only after the implementation style is selected.", - "resource.capability-solution-design-canvas.tips.1": "Keep the Interaction Canvas optional for CRUD, query, command, or event interaction details.", + "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", + "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", + "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", - "resource.capability-readiness-operations-canvas.description": "A canvas for preparing ownership, operations, evidence, support, continuity, change ownership, documentation, risks, readiness status, and improvement backlog.", - "resource.capability-readiness-operations-canvas.outcomes": "Documented capability decision or working artifact", - "resource.capability-readiness-operations-canvas.outcomes.1": "Consumer, producer, owner, evidence, constraints, and service expectations clarified", - "resource.capability-readiness-operations-canvas.outcomes.2": "Risks, assumptions, next steps, and lifecycle implications visible", - "resource.capability-readiness-operations-canvas.steps": "Clarify the capability purpose, consumers, producers, scope, and evidence.", - "resource.capability-readiness-operations-canvas.steps.1": "Document decisions, responsibilities, service expectations, risks, and required artifacts.", - "resource.capability-readiness-operations-canvas.steps.2": "Use the output for architecture, design, delivery, readiness, publishing, or improvement.", - "resource.capability-readiness-operations-canvas.tips": "Use style-specific API, integration, workflow, data product, or application guidance only after the implementation style is selected.", - "resource.capability-readiness-operations-canvas.tips.1": "Keep supporting canvases optional evidence rather than mandatory work.", + "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", + "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", + "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-consumer-onboarding-guide.title": "Capability Consumer Onboarding Guide", "resource.capability-consumer-onboarding-guide.description": "Guidance for helping consumers discover, evaluate, request access to, test, onboard, and begin using a reusable capability.", "resource.capability-consumer-onboarding-guide.outcomes": "Documented capability decision or working artifact", diff --git a/src/data/method/fi/labels.cycles.json b/src/data/method/fi/labels.cycles.json index 49388f2..457dbfc 100644 --- a/src/data/method/fi/labels.cycles.json +++ b/src/data/method/fi/labels.cycles.json @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "API-julkaisu", "cycle.station.monitoring-and-improving": "APIen seuranta ja parantaminen", "cycle.station.integration-capability-strategy": "Integraatiokyvykkyyden strategia", - "cycle.station.integration-consumer-requirements-onboarding": "Integraation hyödyntäjien vaatimukset ja käyttöönotto", + "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", "cycle.station.integration-architecture-decision": "Integraatioarkkitehtuuri ja alustapaatokset", "cycle.station.integration-solution-design": "Integraation ratkaisusuunnittelu", "cycle.station.integration-delivery-operations": "Integraation toimitus ja operointi", @@ -61,7 +61,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Seuraa APIen tilaa, käyttöönottoa, hyödyntäjien tuloksia, luotettavuutta ja parannusmahdollisuuksia julkaisun jälkeen.", "cycle.automation-cycle.title": "Automaatiosykli", "cycle.automation-cycle.description": "Sykli automaatioratkaisujen valintaan, suunnitteluun, toimittamiseen, käyttöönottoon ja parantamiseen ihmisten, sääntöjen, työnkulkujen, agenttien, integraatioiden, käyttöliittymäautomaation ja operoinnin yli.", - "cycle.automation-cycle.purpose": "Guide teams from a validated automation opportunity to a governed, operable automation solution by deciding what each step should be performed by: a person, rule, workflow, agent, API or system integration, connector, custom code, or UI automation.", + "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", "cycle.audience.automation-owners": "Automaation omistajat", "cycle.audience.process-owners": "Prosessinomistajat", "cycle.audience.automation-teams": "Automaatiotiimit", @@ -71,33 +71,33 @@ "cycle.station.automation-readiness-review": "Automaation valmiuskatselmointi", "cycle.station.automation-enablement": "Automaation kayttoonotto ja kayttoonoton tuki", "cycle.station.automation-monitoring-improvement": "Automaation seuranta ja parantaminen", - "cycle.automation-cycle.station.api-product-strategy.description": "Prioritize a testable automation hypothesis. Use Customer Journey, Capability Value Proposition, Domain, Business Impact, Capacity, or other canvases only as optional supporting evidence where relevant.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Create the initial human-automation responsibility allocation and capture user, operator, permission, activation, support, recovery, observability, and non-functional requirements before implementation choices are made.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Evaluate and justify the automation architecture and implementation approach against requirements, responsibility assumptions, feasibility, security, reliability, operability, cost, and risk.", - "cycle.automation-cycle.station.api-design.description": "Design the automation workflow sequence, states, triggers, data, decisions, system interactions, handoffs, exceptions, evidence, monitoring points, and recovery paths.", + "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", + "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", "cycle.automation-cycle.station.api-audit.description": "Käytä valmiustarkistuslistaa näytön arviointiin ja julkaisupäätöksen kirjaamiseen: valmis, ehdollisesti valmis, korjaus tarvitaan tai ei hyväksytty.", "cycle.automation-cycle.station.api-publishing.description": "Aktivoi ja ota automaatio turvallisesti käyttöön viestinnän, koulutuksen, toimintaohjeiden, tukipolkujen, käyttöönoton seurannan, palautekanavien, vaiheistetun rollout-suunnitelman sekä pysäytys- ja palautusehtojen avulla.", "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process, User & Automation Requirements", + "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Priorisoi uudelleenkäytettävä integraatiokyvykkyyshypoteesi kuluttaja-, arvo-, domain-, omistajuus-, uudelleenkäyttö- ja elinkelpoisuusnäytön avulla.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Kuvaa integraation kuluttajat, tarjoajan vastuut, onboarding-tarpeet, palveluodotukset ja operatiiviset reunaehdot.", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Valitse integraatioarkkitehtuuri, toteutustyyli ja alustakyvykkyydet reunaehtojen ja governancen perusteella.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Suunnittele integraatioratkaisu, sopimukset, skeemat, tietorakenteet, mäppäykset sekä vuorovaikutus- tai toimitusmallit valitulle tyylille.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Rakenna, testaa, deployaa ja operoi integraatiokyvykkyys valitun toteutustyylin ja validoidun sopimuksen mukaisesti.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Varmista integraation valmius, governance, laatu, security, compliance ja operatiivinen näyttö ennen julkaisua.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Julkaise integraatiokyvykkyys, jotta tiimit voivat löytää sen, arvioida sen, pyytää pääsyä, onboardata, käyttää uudelleen ja saada tukea.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Seuraa integraation luotettavuutta, uudelleenkäyttöä, incidentejä, suorituskykyä, kuluttajatuloksia ja parannustarpeita.", - "cycle.station.consumer-producer-service-requirements": "Kuluttaja-, tuottaja- ja palveluvaatimukset", + "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", "cycle.station.capability-architecture-platform-decisions": "Kyvykkyyden arkkitehtuuri- ja alustapäätökset", "cycle.station.capability-solution-interaction-design": "Kyvykkyysratkaisun ja vuorovaikutuksen suunnittelu", "cycle.station.capability-delivery-operations": "Kyvykkyyden toimitus ja operointi", "cycle.station.capability-readiness-assurance": "Kyvykkyyden valmiuden varmistus", "cycle.station.capability-publishing-enablement": "Kyvykkyyden julkaisu ja enablement", "cycle.station.capability-monitoring-improvement": "Kyvykkyyden seuranta ja parantaminen", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Kyvykkyysstrategia: Ohjaa uudelleenkäytettävän kyvykkyyden määrittelyä hypoteesista ja kuluttaja-/tuottajavaatimuksista arkkitehtuuriin, ratkaisusuunnitteluun, toimitukseen, valmiuteen, julkaisuun ja jatkuvaan parantamiseen.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Kuluttaja-, tuottaja- ja palveluvaatimukset: Ohjaa uudelleenkäytettävän kyvykkyyden määrittelyä hypoteesista ja kuluttaja-/tuottajavaatimuksista arkkitehtuuriin, ratkaisusuunnitteluun, toimitukseen, valmiuteen, julkaisuun ja jatkuvaan parantamiseen.", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Kyvykkyyden arkkitehtuuri- ja alustapäätökset: Ohjaa uudelleenkäytettävän kyvykkyyden määrittelyä hypoteesista ja kuluttaja-/tuottajavaatimuksista arkkitehtuuriin, ratkaisusuunnitteluun, toimitukseen, valmiuteen, julkaisuun ja jatkuvaan parantamiseen.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Kyvykkyysratkaisun ja vuorovaikutuksen suunnittelu: Ohjaa uudelleenkäytettävän kyvykkyyden määrittelyä hypoteesista ja kuluttaja-/tuottajavaatimuksista arkkitehtuuriin, ratkaisusuunnitteluun, toimitukseen, valmiuteen, julkaisuun ja jatkuvaan parantamiseen.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Kyvykkyyden toimitus ja operointi: Ohjaa uudelleenkäytettävän kyvykkyyden määrittelyä hypoteesista ja kuluttaja-/tuottajavaatimuksista arkkitehtuuriin, ratkaisusuunnitteluun, toimitukseen, valmiuteen, julkaisuun ja jatkuvaan parantamiseen.", diff --git a/src/data/method/fi/labels.resources.json b/src/data/method/fi/labels.resources.json index 96cbbf8..05be628 100644 --- a/src/data/method/fi/labels.resources.json +++ b/src/data/method/fi/labels.resources.json @@ -159,11 +159,11 @@ "resource.capacity-canvas.outcomes": "Liiketoiminnan odotettuun kysyntään sovitetut kapasiteettivaatimukset", "resource.capacity-canvas.steps": "Current Business Volumes: Quantify current business volumes and transaction rates.", "resource.capacity-canvas.tips": "Use requirements canvases to capture what users need; use this canvas to quantify demand and inform scaling decisions.", - "resource.customer-journey-canvas.title": "Asiakaspolkukanvas", - "resource.customer-journey-canvas.description": "Kartoittaa asiakkaan tai käyttäjän polun tarpeiden ja kipupisteiden tunnistamiseksi, jotta kyvykkyyden ja rajapinnan suunnittelu perustuu todelliseen kontekstiin.", - "resource.customer-journey-canvas.outcomes": "Yhteinen ymmärrys asiakkaan, kumppanin tai hyödyntäjän polusta", - "resource.customer-journey-canvas.steps": "Määrittele asiakaspersoona", - "resource.customer-journey-canvas.tips": "Validoi polku niiden ihmisten kanssa, jotka toteuttavat sen tai kokevat sen.", + "resource.customer-journey-canvas.title": "Customer Journey Canvas", + "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", + "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", + "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", "resource.event-canvas.title": "Tapahtumakanvas", "resource.event-canvas.description": "Suunnittele tapahtumapohjaiset rajapinnat ja integraatiot määrittelemällä tapahtumat, laukaisimet, skeemat, tuottajat, hyödyntäjät ja käsittelylogiikka.", "resource.event-canvas.outcomes": "Määritelty tapahtumapohjainen vuorovaikutusmalli", @@ -352,16 +352,16 @@ "resource.capacity-canvas.steps.4": "Ehdotetaan skaalausstrategioita", "resource.capacity-canvas.tips.1": "Käytä mitattua tietoa aina kun sitä on saatavilla ja kirjaa oletukset näkyviin.", "resource.capacity-canvas.tips.2": "Päivitä kanvas pilotin tai kysynnän olennaisten muutosten jälkeen.", - "resource.customer-journey-canvas.outcomes.1": "Dokumentoidut tarpeet, kipupisteet, hyödyt, syötteet ja tuotokset", - "resource.customer-journey-canvas.outcomes.2": "Polkua koskeva näyttö kyvykkyys-, vaatimus- ja arkkitehtuuripäätösten tueksi", - "resource.customer-journey-canvas.steps.1": "Tunnista matkan käynnistäjät", - "resource.customer-journey-canvas.steps.2": "Kuvaile matkan loppua", + "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", "resource.customer-journey-canvas.steps.3": "Kartoita matkan vaiheet ja syötteet/lähtötiedot", "resource.customer-journey-canvas.steps.4": "Tunnista asiakkaan kipupisteet", "resource.customer-journey-canvas.steps.5": "Yhteenveto asiakkaan saamista eduista", "resource.customer-journey-canvas.steps.6": "Määritellään tarvittavat syötteet ja tuotokset", "resource.customer-journey-canvas.steps.7": "Määrittele API-vuorovaikutukset kullekin vaiheelle", - "resource.customer-journey-canvas.tips.1": "Hyödynnä tuloksia arvolupauksen, toimialueen, vaatimusten ja arkkitehtuurin työstämisessä.", + "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.event-canvas.outcomes.1": "Selkeytetyt tapahtumat, laukaisimet, skeemat, tuottajat ja hyödyntäjät", "resource.event-canvas.outcomes.2": "Dokumentoidut käsittely-, kuittaus- ja virhetilanneodotukset", "resource.event-canvas.steps.1": "Määritä laukaisimet kullekin tapahtumalle", @@ -542,56 +542,46 @@ "resource.api-testing-best-practices.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.", "resource.apiops-CI-CD-for-apis.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.", "resource.api-audit-checklist.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.", - "resource.automation-opportunity-canvas.title": "Automaation hypoteesikanvas", - "resource.automation-opportunity-canvas.description": "A compact primary canvas for linking optional supporting evidence to a testable automation hypothesis and validation decision.", - "resource.automation-opportunity-canvas.outcomes": "Testable automation hypothesis", - "resource.automation-opportunity-canvas.outcomes.1": "Supporting evidence, scope, assumptions, and validation experiment linked without duplicating other canvases", - "resource.automation-opportunity-canvas.outcomes.2": "Evidence-based decision to proceed, revise, redesign the process, or reject", - "resource.automation-opportunity-canvas.steps": "State the automation hypothesis and reference Journey, Value Proposition, Domain, Business Impact, Capacity, or other evidence only where relevant.", - "resource.automation-opportunity-canvas.steps.1": "Define the automation scope, out-of-scope work, and initial implementation hypothesis without making an architecture decision.", - "resource.automation-opportunity-canvas.steps.2": "Identify critical assumptions, design the smallest useful validation experiment, and record the decision after reviewing evidence.", - "resource.automation-opportunity-canvas.tips": "Treat Customer Journey, Capability Value Proposition, Domain, Business Impact, and Capacity as optional supporting evidence, not required outputs for every automation opportunity.", - "resource.automation-opportunity-canvas.tips.1": "Stop, narrow, or redesign weak opportunities before implementation choices become locked.", - "resource.human-automation-responsibility-canvas.title": "Human-Automation Responsibility Canvas", - "resource.human-automation-responsibility-canvas.description": "A canvas for creating the initial allocation of what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "resource.human-automation-responsibility-canvas.outcomes": "Clear human and automation responsibilities", - "resource.human-automation-responsibility-canvas.outcomes.1": "Oversight, escalation, and audit evidence defined by process step", - "resource.human-automation-responsibility-canvas.outcomes.2": "Implementation mechanisms selected without assuming every step should be automated", - "resource.human-automation-responsibility-canvas.steps": "List the target process steps and current handoffs.", - "resource.human-automation-responsibility-canvas.steps.1": "Assign each step to people, rules, workflows, agents, systems, APIs, UI automation, or a hybrid responsibility.", - "resource.human-automation-responsibility-canvas.steps.2": "Define oversight, escalation, and evidence for each step so later architecture and workflow design can validate and refine the allocation.", - "resource.human-automation-responsibility-canvas.tips": "Keep accountability visible even when execution is automated.", - "resource.human-automation-responsibility-canvas.tips.1": "Revisit this canvas later only to validate architecture assumptions or refine workflow-level handoffs and exceptions.", + "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", + "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", + "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "A canvas for designing the automation sequence, states, data, triggers, decisions, system interactions, failure paths, evidence, monitoring, and recovery.", - "resource.automation-workflow-canvas.outcomes": "Testable automation workflow design", - "resource.automation-workflow-canvas.outcomes.1": "Triggers, stages, states, decisions, data, interactions, handoffs, exceptions, and recovery paths defined", - "resource.automation-workflow-canvas.outcomes.2": "Operational evidence and monitoring points identified before delivery", - "resource.automation-workflow-canvas.steps": "Separate the target process from the technical workflow.", - "resource.automation-workflow-canvas.steps.1": "Map triggers, inputs, stages, states, decisions, automation actions, system interactions, data sources, handoffs, outputs, and exceptions.", - "resource.automation-workflow-canvas.steps.2": "Define retries, timeouts, duplicate prevention, audit evidence, monitoring points, and recovery paths.", - "resource.automation-workflow-canvas.tips": "Treat exceptions and manual recovery as part of the design, not an afterthought.", - "resource.automation-workflow-canvas.tips.1": "Revisit the Human-Automation Responsibility Canvas separately to refine responsibility allocation, oversight, escalation, and evidence for the workflow stages now being designed.", + "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", + "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", + "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "A canvas for comparing and justifying alternative implementation mechanisms for an automation solution.", - "resource.automation-architecture-decision-canvas.outcomes": "Justified automation architecture and implementation approach", - "resource.automation-architecture-decision-canvas.outcomes.1": "Candidate mechanisms compared on quality, risk, cost, skills, and operational fit", - "resource.automation-architecture-decision-canvas.outcomes.2": "Hybrid solution decisions documented", - "resource.automation-architecture-decision-canvas.steps": "Merkitse jokainen ehdokasmekanismi tarkastelluksi, valituksi, hylätyksi tai ei-relevantiksi ennen toteuttamiskelpoisten vaihtoehtojen vertailua.", - "resource.automation-architecture-decision-canvas.steps.1": "Evaluate feasibility, reliability, security, maintainability, latency, scalability, cost, vendor dependency, testability, observability, recoverability, skills, and architectural fit.", - "resource.automation-architecture-decision-canvas.steps.2": "Document the preferred hybrid approach, rationale, risks, and open assumptions.", - "resource.automation-architecture-decision-canvas.tips": "Do not force every mechanism into the solution; make irrelevant candidates explicit and compare only viable options.", - "resource.automation-architecture-decision-canvas.tips.1": "Choose UI automation only when more stable system or integration paths are insufficient.", - "resource.automation-readiness-operations-canvas.title": "Automaation valmius- ja operointikanvas", - "resource.automation-readiness-operations-canvas.description": "A canvas for preparing the operating model for a safely released, supported, monitored, and recoverable automation.", - "resource.automation-readiness-operations-canvas.outcomes": "Documented automation operating model", - "resource.automation-readiness-operations-canvas.outcomes.1": "Ownership, permissions, environments, evidence, monitoring, support, fallback, rollback, and risks prepared", - "resource.automation-readiness-operations-canvas.outcomes.2": "Release readiness status and improvement backlog ready for readiness review and post-release learning", - "resource.automation-readiness-operations-canvas.steps": "Prepare business owner, operational owner, affected users, permissions, credentials, environments, and documentation.", - "resource.automation-readiness-operations-canvas.steps.1": "Prepare test evidence, exception handling, monitoring, support, manual fallback, rollback, and known risks.", - "resource.automation-readiness-operations-canvas.steps.2": "Kirjaa julkaisuvalmiuden tila ja parannusbacklog tekemättä muodollista valmiuspäätöstä.", - "resource.automation-readiness-operations-canvas.tips": "Käytä tätä Delivery & Operations -vaiheessa näytön valmisteluun; käytä automaation valmiustarkistuslistaa muodolliseen julkaisupäätökseen.", - "resource.automation-readiness-operations-canvas.tips.1": "Make manual fallback and operational ownership explicit before production use.", + "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", + "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", + "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", + "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", + "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", + "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", @@ -613,46 +603,46 @@ "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", "resource.automation-monitoring-value-metrics.tips": "Seuranta muuntaa operatiivisen, käyttäjä-, riski- ja arvonäytön elinkaaripäätöksiksi ja parannusbacklogiksi.", "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Integraatiokyvykkyyden hypoteesikanvas", - "resource.integration-capability-hypothesis-canvas.description": "Integraatiokyvykkyyden hypoteesikanvas tukee uudelleenkäytettävän integraatiokyvykkyyden suunnittelua, päätöksentekoa, toimitusta, julkaisua tai parantamista.", - "resource.integration-capability-hypothesis-canvas.outcomes": "Dokumentoitu integraation työpohja", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Keskeiset päätökset, vastuut, näyttö ja reunaehdot kirjattu", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "Seuraavat askeleet, riskit ja avoimet asiat näkyvissä integraatiotyötä varten", - "resource.integration-capability-hypothesis-canvas.steps": "Selkeytä tarkoitus, osapuolet, rajaus ja tarvittava näyttö.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Dokumentoi päätökset, ehdot, vastuut ja tarvittavat artefaktit.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Hyödynnä tuloksia suunnittelussa, toimituksessa, valmiusarvioinnissa, julkaisussa tai parantamisessa.", - "resource.integration-capability-hypothesis-canvas.tips": "Sovita tämä resurssi valittuun integraatiotyyliin.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Ota mukaan tuottajat, kuluttajat, alusta, operointi, security, compliance ja business.", - "resource.integration-consumer-provider-requirements-canvas.title": "Integraation kuluttaja- ja tarjoajavaatimusten kanvas", - "resource.integration-consumer-provider-requirements-canvas.description": "Integraation kuluttaja- ja tarjoajavaatimusten kanvas tukee uudelleenkäytettävän integraatiokyvykkyyden suunnittelua, päätöksentekoa, toimitusta, julkaisua tai parantamista.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "Dokumentoitu integraation työpohja", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Keskeiset päätökset, vastuut, näyttö ja reunaehdot kirjattu", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "Seuraavat askeleet, riskit ja avoimet asiat näkyvissä integraatiotyötä varten", - "resource.integration-consumer-provider-requirements-canvas.steps": "Selkeytä tarkoitus, osapuolet, rajaus ja tarvittava näyttö.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Dokumentoi päätökset, ehdot, vastuut ja tarvittavat artefaktit.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Hyödynnä tuloksia suunnittelussa, toimituksessa, valmiusarvioinnissa, julkaisussa tai parantamisessa.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Sovita tämä resurssi valittuun integraatiotyyliin.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Ota mukaan tuottajat, kuluttajat, alusta, operointi, security, compliance ja business.", - "resource.integration-architecture-decision-canvas.title": "Integraation arkkitehtuuripäätöksen kanvas", - "resource.integration-architecture-decision-canvas.description": "Integraation arkkitehtuuripäätöksen kanvas tukee uudelleenkäytettävän integraatiokyvykkyyden suunnittelua, päätöksentekoa, toimitusta, julkaisua tai parantamista.", - "resource.integration-architecture-decision-canvas.outcomes": "Dokumentoitu integraation työpohja", - "resource.integration-architecture-decision-canvas.outcomes.1": "Ehdokastyylit verrattu statuksen kanssa ja valittu tyyli tai hybridi kirjattu", - "resource.integration-architecture-decision-canvas.outcomes.2": "Seuraavat askeleet, riskit ja avoimet asiat näkyvissä integraatiotyötä varten", - "resource.integration-architecture-decision-canvas.steps": "Käytä ehdokasstatus-valintaa merkitäksesi jokaisen tyylin tarkastelluksi, valituksi, hylätyksi tai ei-relevantiksi.", - "resource.integration-architecture-decision-canvas.steps.1": "Dokumentoi päätökset, ehdot, vastuut ja tarvittavat artefaktit.", - "resource.integration-architecture-decision-canvas.steps.2": "Hyödynnä tuloksia suunnittelussa, toimituksessa, valmiusarvioinnissa, julkaisussa tai parantamisessa.", - "resource.integration-architecture-decision-canvas.tips": "Sovita tämä resurssi valittuun integraatiotyyliin.", - "resource.integration-architecture-decision-canvas.tips.1": "Ota mukaan tuottajat, kuluttajat, alusta, operointi, security, compliance ja business.", - "resource.integration-readiness-operations-canvas.title": "Integraation valmius- ja operointikanvas", - "resource.integration-readiness-operations-canvas.description": "Integraation valmius- ja operointikanvas tukee uudelleenkäytettävän integraatiokyvykkyyden suunnittelua, päätöksentekoa, toimitusta, julkaisua tai parantamista.", - "resource.integration-readiness-operations-canvas.outcomes": "Dokumentoitu integraation työpohja", - "resource.integration-readiness-operations-canvas.outcomes.1": "Keskeiset päätökset, vastuut, näyttö ja reunaehdot kirjattu", - "resource.integration-readiness-operations-canvas.outcomes.2": "Seuraavat askeleet, riskit ja avoimet asiat näkyvissä integraatiotyötä varten", - "resource.integration-readiness-operations-canvas.steps": "Selkeytä tarkoitus, osapuolet, rajaus ja tarvittava näyttö.", - "resource.integration-readiness-operations-canvas.steps.1": "Dokumentoi päätökset, ehdot, vastuut ja tarvittavat artefaktit.", - "resource.integration-readiness-operations-canvas.steps.2": "Hyödynnä tuloksia suunnittelussa, toimituksessa, valmiusarvioinnissa, julkaisussa tai parantamisessa.", - "resource.integration-readiness-operations-canvas.tips": "Sovita tämä resurssi valittuun integraatiotyyliin.", - "resource.integration-readiness-operations-canvas.tips.1": "Ota mukaan tuottajat, kuluttajat, alusta, operointi, security, compliance ja business.", + "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", + "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", + "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", + "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", + "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", + "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", + "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", + "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", + "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", + "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-consumer-onboarding-guide.title": "Integraation kuluttaja-onboardingin opas", "resource.integration-consumer-onboarding-guide.description": "Integraation kuluttaja-onboardingin opas tukee uudelleenkäytettävän integraatiokyvykkyyden suunnittelua, päätöksentekoa, toimitusta, julkaisua tai parantamista.", "resource.integration-consumer-onboarding-guide.outcomes": "Dokumentoitu integraation työpohja", @@ -823,66 +813,66 @@ "resource.integration-lifecycle-management-guide.steps.2": "Hyödynnä tuloksia suunnittelussa, toimituksessa, valmiusarvioinnissa, julkaisussa tai parantamisessa.", "resource.integration-lifecycle-management-guide.tips": "Sovita tämä resurssi valittuun integraatiotyyliin.", "resource.integration-lifecycle-management-guide.tips.1": "Ota mukaan tuottajat, kuluttajat, alusta, operointi, security, compliance ja business.", - "resource.integration-solution-design-canvas.title": "Integraatioratkaisun suunnittelukanvas", - "resource.integration-solution-design-canvas.description": "Yhteenvetokanvas integraatiosuunnittelun päätöksille eri tyylien yli, mukaan lukien tyyli, tuottajat, kuluttajat, sopimukset, skeemat, mäppäykset, toimitusmalli, turvallisuus, virheenkäsittely, retry, replay, korrelaatio, täsmäytys, havainnoitavuus ja versiointi.", - "resource.integration-solution-design-canvas.outcomes": "Kokonainen integraatioratkaisun suunnitteluyhteenveto", - "resource.integration-solution-design-canvas.outcomes.1": "Sopimus-, skeema-, mäppäys-, toimitus-, turvallisuus-, recovery- ja havainnoitavuuspäätökset dokumentoitu", - "resource.integration-solution-design-canvas.outcomes.2": "Suunnittelu jäljitettävissä arkkitehtuuripäätökseen ja kuluttaja-/tarjoajavaatimuksiin", - "resource.integration-solution-design-canvas.steps": "Aloita valitusta arkkitehtuurityylistä tai hybridistä.", - "resource.integration-solution-design-canvas.steps.1": "Dokumentoi sopimukset, skeemat, mäppäykset, transformaatiot, toimitusmalli, identiteetti, turvallisuus, virheet, retry, replay, korrelaatio, täsmäytys, havainnoitavuus ja versiointi.", - "resource.integration-solution-design-canvas.steps.2": "Käytä Interaction Canvasia ja tyylikohtaisia resursseja vain, kun syvempää suunnittelutietoa tarvitaan.", - "resource.integration-solution-design-canvas.tips": "Käytä tätä ensisijaisena Integration Solution Design -artefaktina.", - "resource.integration-solution-design-canvas.tips.1": "Kata workflow-orchestratio, B2B/EDI, webhookit, kanoniset datamallit, tiedostot, streamit, messaging, datatuotteet, API:t ja connectorit tarpeen mukaan.", - "resource.capability-hypothesis-canvas.title": "Kyvykkyyshypoteesin kanvas", - "resource.capability-hypothesis-canvas.description": "Kyvykkyyshypoteesin kanvas tukee kyseistä kyvykkyysvaihetta konkreettisilla päätöksillä, näytöllä, vastuilla, riskeillä ja seuraavilla askeleilla.", - "resource.capability-hypothesis-canvas.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "resource.capability-hypothesis-canvas.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "resource.capability-hypothesis-canvas.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "resource.capability-hypothesis-canvas.steps": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "resource.capability-hypothesis-canvas.steps.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "resource.capability-hypothesis-canvas.steps.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "resource.capability-hypothesis-canvas.tips": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "resource.capability-hypothesis-canvas.tips.1": "Pidä tukikanvakset vapaaehtoisena näyttönä, ei pakollisena työnä.", - "resource.capability-consumer-producer-requirements-canvas.title": "Kuluttaja- ja tuottajavaatimusten kanvas", - "resource.capability-consumer-producer-requirements-canvas.description": "Kuluttaja- ja tuottajavaatimusten kanvas tukee kyseistä kyvykkyysvaihetta konkreettisilla päätöksillä, näytöllä, vastuilla, riskeillä ja seuraavilla askeleilla.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "resource.capability-consumer-producer-requirements-canvas.steps": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Pidä tukikanvakset vapaaehtoisena näyttönä, ei pakollisena työnä.", - "resource.capability-architecture-decision-canvas.title": "Kyvykkyyden arkkitehtuuripäätöksen kanvas", - "resource.capability-architecture-decision-canvas.description": "Kyvykkyyden arkkitehtuuripäätöksen kanvas tukee kyseistä kyvykkyysvaihetta konkreettisilla päätöksillä, näytöllä, vastuilla, riskeillä ja seuraavilla askeleilla.", - "resource.capability-architecture-decision-canvas.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "resource.capability-architecture-decision-canvas.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "resource.capability-architecture-decision-canvas.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "resource.capability-architecture-decision-canvas.steps": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "resource.capability-architecture-decision-canvas.steps.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "resource.capability-architecture-decision-canvas.steps.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "resource.capability-architecture-decision-canvas.tips": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "resource.capability-architecture-decision-canvas.tips.1": "Pidä tukikanvakset vapaaehtoisena näyttönä, ei pakollisena työnä.", - "resource.capability-solution-design-canvas.title": "Kyvykkyysratkaisun suunnittelukanvas", - "resource.capability-solution-design-canvas.description": "Kyvykkyysratkaisun suunnittelukanvas tukee kyseistä kyvykkyysvaihetta konkreettisilla päätöksillä, näytöllä, vastuilla, riskeillä ja seuraavilla askeleilla.", - "resource.capability-solution-design-canvas.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "resource.capability-solution-design-canvas.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "resource.capability-solution-design-canvas.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "resource.capability-solution-design-canvas.steps": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "resource.capability-solution-design-canvas.steps.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "resource.capability-solution-design-canvas.steps.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "resource.capability-solution-design-canvas.tips": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "resource.capability-solution-design-canvas.tips.1": "Pidä tukikanvakset vapaaehtoisena näyttönä, ei pakollisena työnä.", - "resource.capability-readiness-operations-canvas.title": "Kyvykkyyden valmius- ja operointikanvas", - "resource.capability-readiness-operations-canvas.description": "Kyvykkyyden valmius- ja operointikanvas tukee kyseistä kyvykkyysvaihetta konkreettisilla päätöksillä, näytöllä, vastuilla, riskeillä ja seuraavilla askeleilla.", - "resource.capability-readiness-operations-canvas.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "resource.capability-readiness-operations-canvas.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "resource.capability-readiness-operations-canvas.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "resource.capability-readiness-operations-canvas.steps": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "resource.capability-readiness-operations-canvas.steps.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "resource.capability-readiness-operations-canvas.steps.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "resource.capability-readiness-operations-canvas.tips": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "resource.capability-readiness-operations-canvas.tips.1": "Pidä tukikanvakset vapaaehtoisena näyttönä, ei pakollisena työnä.", + "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", + "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", + "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", + "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", + "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", + "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", + "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", + "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", + "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", + "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", + "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", + "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", + "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", + "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", + "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", + "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", + "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-consumer-onboarding-guide.title": "Kyvykkyyden kuluttaja-onboardingin opas", "resource.capability-consumer-onboarding-guide.description": "Kyvykkyyden kuluttaja-onboardingin opas tukee kyseistä kyvykkyysvaihetta konkreettisilla päätöksillä, näytöllä, vastuilla, riskeillä ja seuraavilla askeleilla.", "resource.capability-consumer-onboarding-guide.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", diff --git a/src/data/method/fr/labels.cycles.json b/src/data/method/fr/labels.cycles.json index cb7569c..7c35a6a 100644 --- a/src/data/method/fr/labels.cycles.json +++ b/src/data/method/fr/labels.cycles.json @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "Publication d’API", "cycle.station.monitoring-and-improving": "Suivi & amelioration API", "cycle.station.integration-capability-strategy": "Stratégie de capacité d’intégration", - "cycle.station.integration-consumer-requirements-onboarding": "Exigences des utilisateurs d’intégration & onboarding", + "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", "cycle.station.integration-architecture-decision": "Architecture d integration & decisions de plateforme", "cycle.station.integration-solution-design": "Conception de solution d’intégration", "cycle.station.integration-delivery-operations": "Livraison & opérations d’intégration", @@ -61,7 +61,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Suivez la santé de l’API, l’adoption, les résultats utilisateurs, la fiabilité et les opportunités d’amélioration après publication.", "cycle.automation-cycle.title": "Cycle d’automatisation", "cycle.automation-cycle.description": "Un cycle pour sélectionner, concevoir, livrer, déployer et améliorer des solutions d’automatisation couvrant les personnes, règles, workflows, agents, intégrations, automatisation d’interface et opérations.", - "cycle.automation-cycle.purpose": "Guide teams from a validated automation opportunity to a governed, operable automation solution by deciding what each step should be performed by: a person, rule, workflow, agent, API or system integration, connector, custom code, or UI automation.", + "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", "cycle.audience.automation-owners": "Responsables automatisation", "cycle.audience.process-owners": "Responsables de processus", "cycle.audience.automation-teams": "Équipes d’automatisation", @@ -71,33 +71,33 @@ "cycle.station.automation-readiness-review": "Revue de préparation de l’automatisation", "cycle.station.automation-enablement": "Deploiement & enablement de l automatisation", "cycle.station.automation-monitoring-improvement": "Suivi & amélioration de l’automatisation", - "cycle.automation-cycle.station.api-product-strategy.description": "Prioritize a testable automation hypothesis. Use Customer Journey, Capability Value Proposition, Domain, Business Impact, Capacity, or other canvases only as optional supporting evidence where relevant.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Create the initial human-automation responsibility allocation and capture user, operator, permission, activation, support, recovery, observability, and non-functional requirements before implementation choices are made.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Evaluate and justify the automation architecture and implementation approach against requirements, responsibility assumptions, feasibility, security, reliability, operability, cost, and risk.", - "cycle.automation-cycle.station.api-design.description": "Design the automation workflow sequence, states, triggers, data, decisions, system interactions, handoffs, exceptions, evidence, monitoring points, and recovery paths.", + "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", + "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", "cycle.automation-cycle.station.api-audit.description": "Utilisez une checklist de préparation pour examiner les preuves et enregistrer la décision de publication: prêt, prêt sous conditions, remédiation requise ou non approuvé.", "cycle.automation-cycle.station.api-publishing.description": "Activez et déployez l’automatisation en sécurité avec communication, formation, consignes d’exploitation, circuits de support, suivi de l’adoption, canaux de feedback, déploiement progressif, conditions de pause et de rollback.", "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process, User & Automation Requirements", + "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Prioriser une hypothèse de capacité d’intégration réutilisable avec les preuves consommateurs, valeur, domaine, propriété, réutilisation et viabilité.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Capturer les consommateurs d’intégration, responsabilités fournisseur, besoins d’onboarding, attentes de service et contraintes opérationnelles.", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Sélectionner l’architecture d’intégration, le style d’implémentation et les capacités plateforme en tenant compte des contraintes et de la gouvernance.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Concevoir la solution d’intégration, les contrats, schémas, structures de données, mappings et modèles d’interaction ou de livraison pour le style sélectionné.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Construire, tester, déployer et exploiter la capacité d’intégration avec son style d’implémentation sélectionné et son contrat validé.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Assurer la préparation, la gouvernance, la qualité, la sécurité, la conformité et les preuves opérationnelles d’intégration avant publication.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Publier la capacité d’intégration pour que les équipes puissent la découvrir, l’évaluer, demander l’accès, s’onboarder, la réutiliser et obtenir du support.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Surveiller fiabilité, réutilisation, incidents, performance, résultats consommateurs et besoins d’amélioration de l’intégration.", - "cycle.station.consumer-producer-service-requirements": "Exigences consommateur, producteur et service", + "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", "cycle.station.capability-architecture-platform-decisions": "Décisions d’architecture et plateforme de capacité", "cycle.station.capability-solution-interaction-design": "Conception de solution et interaction de capacité", "cycle.station.capability-delivery-operations": "Livraison et opérations de capacité", "cycle.station.capability-readiness-assurance": "Assurance de préparation de capacité", "cycle.station.capability-publishing-enablement": "Publication et enablement de capacité", "cycle.station.capability-monitoring-improvement": "Monitoring et amélioration de capacité", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Stratégie de capacité: Guide la définition d’une capacité réutilisable depuis l’hypothèse et les exigences consommateur/producteur jusqu’à l’architecture, la conception, la livraison, la préparation, la publication et l’amélioration continue.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Exigences consommateur, producteur et service: Guide la définition d’une capacité réutilisable depuis l’hypothèse et les exigences consommateur/producteur jusqu’à l’architecture, la conception, la livraison, la préparation, la publication et l’amélioration continue.", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Décisions d’architecture et plateforme de capacité: Guide la définition d’une capacité réutilisable depuis l’hypothèse et les exigences consommateur/producteur jusqu’à l’architecture, la conception, la livraison, la préparation, la publication et l’amélioration continue.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Conception de solution et interaction de capacité: Guide la définition d’une capacité réutilisable depuis l’hypothèse et les exigences consommateur/producteur jusqu’à l’architecture, la conception, la livraison, la préparation, la publication et l’amélioration continue.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Livraison et opérations de capacité: Guide la définition d’une capacité réutilisable depuis l’hypothèse et les exigences consommateur/producteur jusqu’à l’architecture, la conception, la livraison, la préparation, la publication et l’amélioration continue.", diff --git a/src/data/method/fr/labels.resources.json b/src/data/method/fr/labels.resources.json index d4a4386..4f79647 100644 --- a/src/data/method/fr/labels.resources.json +++ b/src/data/method/fr/labels.resources.json @@ -160,10 +160,10 @@ "resource.capacity-canvas.steps": "Current Business Volumes: Quantify current business volumes and transaction rates.", "resource.capacity-canvas.tips": "Use requirements canvases to capture what users need; use this canvas to quantify demand and inform scaling decisions.", "resource.customer-journey-canvas.title": "Customer Journey Canvas", - "resource.customer-journey-canvas.description": "Cartographier les parcours des clients pour identifier les besoins et les points de douleur, afin d'améliorer la conception de l'API et l'expérience de l'utilisateur.", - "resource.customer-journey-canvas.outcomes": "Compréhension partagée du parcours client, partenaire ou utilisateur", - "resource.customer-journey-canvas.steps": "Définir le profil du client", - "resource.customer-journey-canvas.tips": "Validez le parcours avec les personnes qui le réalisent ou le vivent.", + "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", + "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", + "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", "resource.event-canvas.title": "Event Canvas", "resource.event-canvas.description": "Concevez des interfaces et intégrations événementielles en définissant les événements, déclencheurs, schémas, producteurs, utilisateurs et logiques de traitement.", "resource.event-canvas.outcomes": "Modèle d’interaction événementiel défini", @@ -352,16 +352,16 @@ "resource.capacity-canvas.steps.4": "Proposer des stratégies de mise à l'échelle", "resource.capacity-canvas.tips.1": "Utilisez des données mesurées lorsqu’elles sont disponibles et explicitez les hypothèses.", "resource.capacity-canvas.tips.2": "Réexaminez le canvas après les pilotes ou tout changement significatif de la demande.", - "resource.customer-journey-canvas.outcomes.1": "Besoins, irritants, gains, entrées et sorties documentés", - "resource.customer-journey-canvas.outcomes.2": "Éléments du parcours disponibles pour les décisions de capacité, d’exigences et d’architecture", - "resource.customer-journey-canvas.steps.1": "Identifier les éléments déclencheurs du voyage", - "resource.customer-journey-canvas.steps.2": "Décrire la fin du voyage", + "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", "resource.customer-journey-canvas.steps.3": "Cartographier les étapes du voyage avec les intrants et les extrants", "resource.customer-journey-canvas.steps.4": "Identifier les problèmes des clients", "resource.customer-journey-canvas.steps.5": "Résumer les gains pour les clients", "resource.customer-journey-canvas.steps.6": "Définir les intrants nécessaires et les résultats qui en découlent", "resource.customer-journey-canvas.steps.7": "Définir les interactions API pour chaque étape", - "resource.customer-journey-canvas.tips.1": "Utilisez les résultats pour alimenter le travail sur la proposition de valeur, le domaine, les exigences et l’architecture.", + "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.event-canvas.outcomes.1": "Événements, déclencheurs, schémas, producteurs et utilisateurs clarifiés", "resource.event-canvas.outcomes.2": "Attentes de traitement, d’accusé de réception et de gestion des échecs documentées", "resource.event-canvas.steps.1": "Définir des déclencheurs pour chaque événement", @@ -542,56 +542,46 @@ "resource.api-testing-best-practices.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.", "resource.apiops-CI-CD-for-apis.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.", "resource.api-audit-checklist.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.", - "resource.automation-opportunity-canvas.title": "Canvas d’hypothèse d’automatisation", - "resource.automation-opportunity-canvas.description": "A compact primary canvas for linking optional supporting evidence to a testable automation hypothesis and validation decision.", - "resource.automation-opportunity-canvas.outcomes": "Testable automation hypothesis", - "resource.automation-opportunity-canvas.outcomes.1": "Supporting evidence, scope, assumptions, and validation experiment linked without duplicating other canvases", - "resource.automation-opportunity-canvas.outcomes.2": "Evidence-based decision to proceed, revise, redesign the process, or reject", - "resource.automation-opportunity-canvas.steps": "State the automation hypothesis and reference Journey, Value Proposition, Domain, Business Impact, Capacity, or other evidence only where relevant.", - "resource.automation-opportunity-canvas.steps.1": "Define the automation scope, out-of-scope work, and initial implementation hypothesis without making an architecture decision.", - "resource.automation-opportunity-canvas.steps.2": "Identify critical assumptions, design the smallest useful validation experiment, and record the decision after reviewing evidence.", - "resource.automation-opportunity-canvas.tips": "Treat Customer Journey, Capability Value Proposition, Domain, Business Impact, and Capacity as optional supporting evidence, not required outputs for every automation opportunity.", - "resource.automation-opportunity-canvas.tips.1": "Stop, narrow, or redesign weak opportunities before implementation choices become locked.", - "resource.human-automation-responsibility-canvas.title": "Human-Automation Responsibility Canvas", - "resource.human-automation-responsibility-canvas.description": "A canvas for creating the initial allocation of what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "resource.human-automation-responsibility-canvas.outcomes": "Clear human and automation responsibilities", - "resource.human-automation-responsibility-canvas.outcomes.1": "Oversight, escalation, and audit evidence defined by process step", - "resource.human-automation-responsibility-canvas.outcomes.2": "Implementation mechanisms selected without assuming every step should be automated", - "resource.human-automation-responsibility-canvas.steps": "List the target process steps and current handoffs.", - "resource.human-automation-responsibility-canvas.steps.1": "Assign each step to people, rules, workflows, agents, systems, APIs, UI automation, or a hybrid responsibility.", - "resource.human-automation-responsibility-canvas.steps.2": "Define oversight, escalation, and evidence for each step so later architecture and workflow design can validate and refine the allocation.", - "resource.human-automation-responsibility-canvas.tips": "Keep accountability visible even when execution is automated.", - "resource.human-automation-responsibility-canvas.tips.1": "Revisit this canvas later only to validate architecture assumptions or refine workflow-level handoffs and exceptions.", + "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", + "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", + "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "A canvas for designing the automation sequence, states, data, triggers, decisions, system interactions, failure paths, evidence, monitoring, and recovery.", - "resource.automation-workflow-canvas.outcomes": "Testable automation workflow design", - "resource.automation-workflow-canvas.outcomes.1": "Triggers, stages, states, decisions, data, interactions, handoffs, exceptions, and recovery paths defined", - "resource.automation-workflow-canvas.outcomes.2": "Operational evidence and monitoring points identified before delivery", - "resource.automation-workflow-canvas.steps": "Separate the target process from the technical workflow.", - "resource.automation-workflow-canvas.steps.1": "Map triggers, inputs, stages, states, decisions, automation actions, system interactions, data sources, handoffs, outputs, and exceptions.", - "resource.automation-workflow-canvas.steps.2": "Define retries, timeouts, duplicate prevention, audit evidence, monitoring points, and recovery paths.", - "resource.automation-workflow-canvas.tips": "Treat exceptions and manual recovery as part of the design, not an afterthought.", - "resource.automation-workflow-canvas.tips.1": "Revisit the Human-Automation Responsibility Canvas separately to refine responsibility allocation, oversight, escalation, and evidence for the workflow stages now being designed.", + "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", + "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", + "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "A canvas for comparing and justifying alternative implementation mechanisms for an automation solution.", - "resource.automation-architecture-decision-canvas.outcomes": "Justified automation architecture and implementation approach", - "resource.automation-architecture-decision-canvas.outcomes.1": "Candidate mechanisms compared on quality, risk, cost, skills, and operational fit", - "resource.automation-architecture-decision-canvas.outcomes.2": "Hybrid solution decisions documented", - "resource.automation-architecture-decision-canvas.steps": "Marquez chaque mécanisme candidat comme considéré, sélectionné, rejeté ou non pertinent avant de comparer les options viables.", - "resource.automation-architecture-decision-canvas.steps.1": "Evaluate feasibility, reliability, security, maintainability, latency, scalability, cost, vendor dependency, testability, observability, recoverability, skills, and architectural fit.", - "resource.automation-architecture-decision-canvas.steps.2": "Document the preferred hybrid approach, rationale, risks, and open assumptions.", - "resource.automation-architecture-decision-canvas.tips": "Do not force every mechanism into the solution; make irrelevant candidates explicit and compare only viable options.", - "resource.automation-architecture-decision-canvas.tips.1": "Choose UI automation only when more stable system or integration paths are insufficient.", - "resource.automation-readiness-operations-canvas.title": "Canvas de préparation et d’exploitation de l’automatisation", - "resource.automation-readiness-operations-canvas.description": "A canvas for preparing the operating model for a safely released, supported, monitored, and recoverable automation.", - "resource.automation-readiness-operations-canvas.outcomes": "Documented automation operating model", - "resource.automation-readiness-operations-canvas.outcomes.1": "Ownership, permissions, environments, evidence, monitoring, support, fallback, rollback, and risks prepared", - "resource.automation-readiness-operations-canvas.outcomes.2": "Release readiness status and improvement backlog ready for readiness review and post-release learning", - "resource.automation-readiness-operations-canvas.steps": "Prepare business owner, operational owner, affected users, permissions, credentials, environments, and documentation.", - "resource.automation-readiness-operations-canvas.steps.1": "Prepare test evidence, exception handling, monitoring, support, manual fallback, rollback, and known risks.", - "resource.automation-readiness-operations-canvas.steps.2": "Enregistrez le statut de préparation à la publication et le backlog d’amélioration sans prendre la décision formelle de préparation.", - "resource.automation-readiness-operations-canvas.tips": "Utilisez ceci pendant Delivery & Operations pour préparer les preuves; utilisez la checklist de préparation de l’automatisation pour la décision formelle de publication.", - "resource.automation-readiness-operations-canvas.tips.1": "Make manual fallback and operational ownership explicit before production use.", + "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", + "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", + "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", + "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", + "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", + "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", @@ -613,46 +603,46 @@ "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", "resource.automation-monitoring-value-metrics.tips": "Le monitoring transforme les preuves opérationnelles, utilisateur, risque et valeur en décisions de cycle de vie et en backlog d’amélioration.", "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Canvas d’hypothèse de capacité d’intégration", - "resource.integration-capability-hypothesis-canvas.description": "Canvas d’hypothèse de capacité d’intégration soutient la planification, la décision, la livraison, la publication ou l’amélioration d’une capacité d’intégration réutilisable.", - "resource.integration-capability-hypothesis-canvas.outcomes": "Base de travail d’intégration documentée", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Décisions, responsabilités, preuves et contraintes clés documentées", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "Prochaines étapes, risques et points ouverts visibles pour le travail d’intégration", - "resource.integration-capability-hypothesis-canvas.steps": "Clarifiez l’objectif, les parties prenantes, le périmètre et les preuves pertinentes.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Documentez les décisions, conditions, responsabilités et artefacts nécessaires.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Utilisez les résultats pour la conception, la livraison, la préparation, la publication ou l’amélioration.", - "resource.integration-capability-hypothesis-canvas.tips": "Adaptez cette ressource au style d’intégration choisi.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Incluez producteurs, consommateurs, plateforme, opérations, sécurité, conformité et métier.", - "resource.integration-consumer-provider-requirements-canvas.title": "Canvas des exigences consommateur et fournisseur d’intégration", - "resource.integration-consumer-provider-requirements-canvas.description": "Canvas des exigences consommateur et fournisseur d’intégration soutient la planification, la décision, la livraison, la publication ou l’amélioration d’une capacité d’intégration réutilisable.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "Base de travail d’intégration documentée", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Décisions, responsabilités, preuves et contraintes clés documentées", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "Prochaines étapes, risques et points ouverts visibles pour le travail d’intégration", - "resource.integration-consumer-provider-requirements-canvas.steps": "Clarifiez l’objectif, les parties prenantes, le périmètre et les preuves pertinentes.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Documentez les décisions, conditions, responsabilités et artefacts nécessaires.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Utilisez les résultats pour la conception, la livraison, la préparation, la publication ou l’amélioration.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Adaptez cette ressource au style d’intégration choisi.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Incluez producteurs, consommateurs, plateforme, opérations, sécurité, conformité et métier.", - "resource.integration-architecture-decision-canvas.title": "Canvas de décision d’architecture d’intégration", - "resource.integration-architecture-decision-canvas.description": "Canvas de décision d’architecture d’intégration soutient la planification, la décision, la livraison, la publication ou l’amélioration d’une capacité d’intégration réutilisable.", - "resource.integration-architecture-decision-canvas.outcomes": "Base de travail d’intégration documentée", - "resource.integration-architecture-decision-canvas.outcomes.1": "Styles candidats comparés avec statut, et style ou hybride sélectionné enregistré", - "resource.integration-architecture-decision-canvas.outcomes.2": "Prochaines étapes, risques et points ouverts visibles pour le travail d’intégration", - "resource.integration-architecture-decision-canvas.steps": "Utilisez le contrôle de statut candidat pour marquer chaque style comme considéré, sélectionné, rejeté ou non pertinent.", - "resource.integration-architecture-decision-canvas.steps.1": "Documentez les décisions, conditions, responsabilités et artefacts nécessaires.", - "resource.integration-architecture-decision-canvas.steps.2": "Utilisez les résultats pour la conception, la livraison, la préparation, la publication ou l’amélioration.", - "resource.integration-architecture-decision-canvas.tips": "Adaptez cette ressource au style d’intégration choisi.", - "resource.integration-architecture-decision-canvas.tips.1": "Incluez producteurs, consommateurs, plateforme, opérations, sécurité, conformité et métier.", - "resource.integration-readiness-operations-canvas.title": "Canvas de préparation et d’exploitation de l’intégration", - "resource.integration-readiness-operations-canvas.description": "Canvas de préparation et d’exploitation de l’intégration soutient la planification, la décision, la livraison, la publication ou l’amélioration d’une capacité d’intégration réutilisable.", - "resource.integration-readiness-operations-canvas.outcomes": "Base de travail d’intégration documentée", - "resource.integration-readiness-operations-canvas.outcomes.1": "Décisions, responsabilités, preuves et contraintes clés documentées", - "resource.integration-readiness-operations-canvas.outcomes.2": "Prochaines étapes, risques et points ouverts visibles pour le travail d’intégration", - "resource.integration-readiness-operations-canvas.steps": "Clarifiez l’objectif, les parties prenantes, le périmètre et les preuves pertinentes.", - "resource.integration-readiness-operations-canvas.steps.1": "Documentez les décisions, conditions, responsabilités et artefacts nécessaires.", - "resource.integration-readiness-operations-canvas.steps.2": "Utilisez les résultats pour la conception, la livraison, la préparation, la publication ou l’amélioration.", - "resource.integration-readiness-operations-canvas.tips": "Adaptez cette ressource au style d’intégration choisi.", - "resource.integration-readiness-operations-canvas.tips.1": "Incluez producteurs, consommateurs, plateforme, opérations, sécurité, conformité et métier.", + "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", + "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", + "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", + "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", + "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", + "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", + "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", + "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", + "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", + "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-consumer-onboarding-guide.title": "Guide d’onboarding des consommateurs d’intégration", "resource.integration-consumer-onboarding-guide.description": "Guide d’onboarding des consommateurs d’intégration soutient la planification, la décision, la livraison, la publication ou l’amélioration d’une capacité d’intégration réutilisable.", "resource.integration-consumer-onboarding-guide.outcomes": "Base de travail d’intégration documentée", @@ -823,66 +813,66 @@ "resource.integration-lifecycle-management-guide.steps.2": "Utilisez les résultats pour la conception, la livraison, la préparation, la publication ou l’amélioration.", "resource.integration-lifecycle-management-guide.tips": "Adaptez cette ressource au style d’intégration choisi.", "resource.integration-lifecycle-management-guide.tips.1": "Incluez producteurs, consommateurs, plateforme, opérations, sécurité, conformité et métier.", - "resource.integration-solution-design-canvas.title": "Canvas de conception de solution d’intégration", - "resource.integration-solution-design-canvas.description": "Canvas de synthèse pour les décisions de conception d’intégration tous styles confondus, incluant style, producteurs, consommateurs, contrats, schémas, mappings, modèle de livraison, sécurité, erreurs, retry, replay, corrélation, réconciliation, observabilité et versioning.", - "resource.integration-solution-design-canvas.outcomes": "Synthèse complète de conception de solution d’intégration", - "resource.integration-solution-design-canvas.outcomes.1": "Décisions de contrat, schéma, mapping, livraison, sécurité, récupération et observabilité documentées", - "resource.integration-solution-design-canvas.outcomes.2": "Conception traçable à la décision d’architecture et aux exigences consommateur/fournisseur", - "resource.integration-solution-design-canvas.steps": "Commencez par le style d’architecture ou hybride sélectionné.", - "resource.integration-solution-design-canvas.steps.1": "Documentez contrats, schémas, mappings, transformations, modèle de livraison, identité, sécurité, erreurs, retry, replay, corrélation, réconciliation, observabilité et versioning.", - "resource.integration-solution-design-canvas.steps.2": "Utilisez Interaction Canvas et les ressources propres au style uniquement lorsqu’un détail de conception plus profond est nécessaire.", - "resource.integration-solution-design-canvas.tips": "Utilisez ceci comme artefact principal d’Integration Solution Design.", - "resource.integration-solution-design-canvas.tips.1": "Couvrez orchestration de workflow, B2B/EDI, webhooks, modèles de données canoniques, fichiers, streams, messagerie, produits de données, API et connecteurs lorsque pertinent.", - "resource.capability-hypothesis-canvas.title": "Canvas d’hypothèse de capacité", - "resource.capability-hypothesis-canvas.description": "Canvas d’hypothèse de capacité soutient l’étape de capacité concernée avec des décisions, preuves, responsabilités, risques et prochaines étapes spécifiques.", - "resource.capability-hypothesis-canvas.outcomes": "Décision de capacité ou artefact de travail documenté", - "resource.capability-hypothesis-canvas.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "resource.capability-hypothesis-canvas.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "resource.capability-hypothesis-canvas.steps": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "resource.capability-hypothesis-canvas.steps.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "resource.capability-hypothesis-canvas.steps.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "resource.capability-hypothesis-canvas.tips": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "resource.capability-hypothesis-canvas.tips.1": "Gardez les canvases de support comme preuves optionnelles, pas comme travail obligatoire.", - "resource.capability-consumer-producer-requirements-canvas.title": "Canvas des exigences consommateur et producteur", - "resource.capability-consumer-producer-requirements-canvas.description": "Canvas des exigences consommateur et producteur soutient l’étape de capacité concernée avec des décisions, preuves, responsabilités, risques et prochaines étapes spécifiques.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "Décision de capacité ou artefact de travail documenté", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "resource.capability-consumer-producer-requirements-canvas.steps": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Gardez les canvases de support comme preuves optionnelles, pas comme travail obligatoire.", - "resource.capability-architecture-decision-canvas.title": "Canvas de décision d’architecture de capacité", - "resource.capability-architecture-decision-canvas.description": "Canvas de décision d’architecture de capacité soutient l’étape de capacité concernée avec des décisions, preuves, responsabilités, risques et prochaines étapes spécifiques.", - "resource.capability-architecture-decision-canvas.outcomes": "Décision de capacité ou artefact de travail documenté", - "resource.capability-architecture-decision-canvas.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "resource.capability-architecture-decision-canvas.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "resource.capability-architecture-decision-canvas.steps": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "resource.capability-architecture-decision-canvas.steps.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "resource.capability-architecture-decision-canvas.steps.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "resource.capability-architecture-decision-canvas.tips": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "resource.capability-architecture-decision-canvas.tips.1": "Gardez les canvases de support comme preuves optionnelles, pas comme travail obligatoire.", - "resource.capability-solution-design-canvas.title": "Canvas de conception de solution de capacité", - "resource.capability-solution-design-canvas.description": "Canvas de conception de solution de capacité soutient l’étape de capacité concernée avec des décisions, preuves, responsabilités, risques et prochaines étapes spécifiques.", - "resource.capability-solution-design-canvas.outcomes": "Décision de capacité ou artefact de travail documenté", - "resource.capability-solution-design-canvas.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "resource.capability-solution-design-canvas.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "resource.capability-solution-design-canvas.steps": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "resource.capability-solution-design-canvas.steps.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "resource.capability-solution-design-canvas.steps.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "resource.capability-solution-design-canvas.tips": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "resource.capability-solution-design-canvas.tips.1": "Gardez les canvases de support comme preuves optionnelles, pas comme travail obligatoire.", - "resource.capability-readiness-operations-canvas.title": "Canvas de préparation et d’exploitation de capacité", - "resource.capability-readiness-operations-canvas.description": "Canvas de préparation et d’exploitation de capacité soutient l’étape de capacité concernée avec des décisions, preuves, responsabilités, risques et prochaines étapes spécifiques.", - "resource.capability-readiness-operations-canvas.outcomes": "Décision de capacité ou artefact de travail documenté", - "resource.capability-readiness-operations-canvas.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "resource.capability-readiness-operations-canvas.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "resource.capability-readiness-operations-canvas.steps": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "resource.capability-readiness-operations-canvas.steps.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "resource.capability-readiness-operations-canvas.steps.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "resource.capability-readiness-operations-canvas.tips": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "resource.capability-readiness-operations-canvas.tips.1": "Gardez les canvases de support comme preuves optionnelles, pas comme travail obligatoire.", + "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", + "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", + "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", + "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", + "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", + "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", + "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", + "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", + "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", + "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", + "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", + "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", + "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", + "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", + "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", + "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", + "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-consumer-onboarding-guide.title": "Guide d’onboarding consommateur de capacité", "resource.capability-consumer-onboarding-guide.description": "Guide d’onboarding consommateur de capacité soutient l’étape de capacité concernée avec des décisions, preuves, responsabilités, risques et prochaines étapes spécifiques.", "resource.capability-consumer-onboarding-guide.outcomes": "Décision de capacité ou artefact de travail documenté", diff --git a/src/data/method/lines.json b/src/data/method/lines.json index 211efb0..3e7df9e 100644 --- a/src/data/method/lines.json +++ b/src/data/method/lines.json @@ -20,11 +20,7 @@ "market-insights", "business-goals", "competitive-analysis", - "ecosystem-vision", - "integration-monitoring-improvement", - "integration-capability-strategy", - "capability-monitoring-improvement", - "capability-strategy" + "ecosystem-vision" ] }, { @@ -42,13 +38,7 @@ "legal-and-compliance", "security-and-privacy", "design-standards", - "vendor-management", - "integration-capability-strategy", - "integration-consumer-requirements-onboarding", - "integration-architecture-platform-decisions", - "capability-strategy", - "capability-consumer-producer-requirements", - "capability-architecture-platform-decisions" + "vendor-management" ] }, { @@ -62,15 +52,7 @@ "api-platform-architecture", "api-design", "api-delivery", - "api-audit", - "integration-architecture-platform-decisions", - "integration-solution-design", - "integration-delivery-operations", - "integration-readiness-assurance", - "capability-architecture-platform-decisions", - "capability-solution-interaction-design", - "capability-delivery-operations", - "capability-readiness-assurance" + "api-audit" ] }, { @@ -86,9 +68,7 @@ "development", "ci-cd", "test-automation", - "release-management", - "integration-delivery-operations", - "capability-delivery-operations" + "release-management" ] }, { @@ -105,13 +85,7 @@ "service-agreements", "api-consumer-adoption", "api-promotion", - "partner-integration", - "integration-readiness-assurance", - "integration-publishing-enablement", - "integration-monitoring-improvement", - "capability-readiness-assurance", - "capability-publishing-enablement", - "capability-monitoring-improvement" + "partner-integration" ] }, { @@ -128,9 +102,7 @@ "upskilling", "operating-guidelines", "portfolio-management", - "budget-and-resource-management", - "integration-capability-strategy", - "capability-strategy" + "budget-and-resource-management" ] } ] diff --git a/src/data/method/pt/labels.cycles.json b/src/data/method/pt/labels.cycles.json index 22280cd..89bc7ef 100644 --- a/src/data/method/pt/labels.cycles.json +++ b/src/data/method/pt/labels.cycles.json @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "Publicação da API", "cycle.station.monitoring-and-improving": "Monitorizacao e melhoria da API", "cycle.station.integration-capability-strategy": "Estratégia da capacidade de integração", - "cycle.station.integration-consumer-requirements-onboarding": "Requisitos e integração de consumidores da integração", + "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", "cycle.station.integration-architecture-decision": "Arquitetura de integracao e decisoes de plataforma", "cycle.station.integration-solution-design": "Conceção da solução de integração", "cycle.station.integration-delivery-operations": "Entrega e operações da integração", @@ -47,7 +47,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitorize a saúde da API, a adoção, os resultados dos consumidores, a fiabilidade e as oportunidades de melhoria após a disponibilização.", "cycle.automation-cycle.title": "Ciclo de Automação", "cycle.automation-cycle.description": "Um ciclo para selecionar, desenhar, entregar, ativar e melhorar soluções de automação envolvendo pessoas, regras, fluxos de trabalho, agentes, integrações, automação de interface e operações.", - "cycle.automation-cycle.purpose": "Guide teams from a validated automation opportunity to a governed, operable automation solution by deciding what each step should be performed by: a person, rule, workflow, agent, API or system integration, connector, custom code, or UI automation.", + "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", "cycle.audience.automation-owners": "Responsáveis pela automação", "cycle.audience.process-owners": "Responsáveis pelo processo", "cycle.audience.automation-teams": "Equipas de automação", @@ -57,33 +57,33 @@ "cycle.station.automation-readiness-review": "Revisão de prontidão da automação", "cycle.station.automation-enablement": "Rollout e enablement da automação", "cycle.station.automation-monitoring-improvement": "Monitorização e melhoria da automação", - "cycle.automation-cycle.station.api-product-strategy.description": "Prioritize a testable automation hypothesis. Use Customer Journey, Capability Value Proposition, Domain, Business Impact, Capacity, or other canvases only as optional supporting evidence where relevant.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Create the initial human-automation responsibility allocation and capture user, operator, permission, activation, support, recovery, observability, and non-functional requirements before implementation choices are made.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Evaluate and justify the automation architecture and implementation approach against requirements, responsibility assumptions, feasibility, security, reliability, operability, cost, and risk.", - "cycle.automation-cycle.station.api-design.description": "Design the automation workflow sequence, states, triggers, data, decisions, system interactions, handoffs, exceptions, evidence, monitoring points, and recovery paths.", + "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", + "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", "cycle.automation-cycle.station.api-audit.description": "Use uma checklist de prontidão para rever evidências e registar a decisão de lançamento: pronto, pronto com condições, correção necessária ou não aprovado.", "cycle.automation-cycle.station.api-publishing.description": "Ative e implemente a automação com segurança usando comunicação, formação, instruções operacionais, caminhos de suporte, monitorização da adoção, canais de feedback, rollout faseado, pausa e condições de rollback.", "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process, User & Automation Requirements", + "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Priorizar uma hipótese de capacidade de integração reutilizável com evidências de consumidores, valor, domínio, ownership, reutilização e viabilidade.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Capturar consumidores de integração, responsabilidades do provider, necessidades de onboarding, expectativas de serviço e restrições operacionais.", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Selecionar arquitetura de integração, estilo de implementação e capacidades de plataforma considerando restrições e governação.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Desenhar a solução de integração, contratos, esquemas, estruturas de dados, mapeamentos e padrões de interação ou entrega para o estilo selecionado.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Construir, testar, fazer deployment e operar a capacidade de integração usando o estilo selecionado e contrato validado.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Garantir prontidão, governação, qualidade, segurança, compliance e evidências operacionais da integração antes do lançamento.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Publicar a capacidade de integração para que equipas possam descobri-la, avaliá-la, pedir acesso, completar onboarding, reutilizá-la e obter suporte.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Monitorizar fiabilidade, reutilização, incidentes, desempenho, resultados dos consumidores e necessidades de melhoria da integração.", - "cycle.station.consumer-producer-service-requirements": "Requisitos de consumidor, produtor e serviço", + "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", "cycle.station.capability-architecture-platform-decisions": "Decisões de arquitetura e plataforma da capacidade", "cycle.station.capability-solution-interaction-design": "Desenho da solução e interação da capacidade", "cycle.station.capability-delivery-operations": "Entrega e operações da capacidade", "cycle.station.capability-readiness-assurance": "Garantia de prontidão da capacidade", "cycle.station.capability-publishing-enablement": "Publicação e enablement da capacidade", "cycle.station.capability-monitoring-improvement": "Monitorização e melhoria da capacidade", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Estrategia da capacidade: Guia a definição da capacidade reutilizável desde a hipótese e requisitos de consumidor/produtor até arquitetura, desenho da solução, entrega, prontidão, publicação e melhoria contínua.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Requisitos de consumidor, produtor e serviço: Guia a definição da capacidade reutilizável desde a hipótese e requisitos de consumidor/produtor até arquitetura, desenho da solução, entrega, prontidão, publicação e melhoria contínua.", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Decisões de arquitetura e plataforma da capacidade: Guia a definição da capacidade reutilizável desde a hipótese e requisitos de consumidor/produtor até arquitetura, desenho da solução, entrega, prontidão, publicação e melhoria contínua.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Desenho da solução e interação da capacidade: Guia a definição da capacidade reutilizável desde a hipótese e requisitos de consumidor/produtor até arquitetura, desenho da solução, entrega, prontidão, publicação e melhoria contínua.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Entrega e operações da capacidade: Guia a definição da capacidade reutilizável desde a hipótese e requisitos de consumidor/produtor até arquitetura, desenho da solução, entrega, prontidão, publicação e melhoria contínua.", diff --git a/src/data/method/pt/labels.resources.json b/src/data/method/pt/labels.resources.json index 3a998e7..c69827a 100644 --- a/src/data/method/pt/labels.resources.json +++ b/src/data/method/pt/labels.resources.json @@ -322,21 +322,21 @@ "resource.capacity-canvas.tips": "Use requirements canvases to capture what users need; use this canvas to quantify demand and inform scaling decisions.", "resource.capacity-canvas.tips.1": "Definir cenários de picos de utilização", "resource.capacity-canvas.tips.2": "Incluir testes de escalabilidade na fase de planeamento", - "resource.customer-journey-canvas.title": "Canvas do Percurso do Cliente", - "resource.customer-journey-canvas.description": "Mapear os percursos dos clientes para identificar necessidades e pontos problemáticos, melhorando a conceção da API e a experiência do utilizador.", - "resource.customer-journey-canvas.outcomes": "Melhoria da compreensão do cliente", - "resource.customer-journey-canvas.outcomes.1": "Conceção melhorada da API", - "resource.customer-journey-canvas.outcomes.2": "Melhor experiência do utilizador", - "resource.customer-journey-canvas.steps": "Definir a personalidade do cliente", - "resource.customer-journey-canvas.steps.1": "Identificar os factores que desencadeiam a viagem", - "resource.customer-journey-canvas.steps.2": "Descrever o fim da viagem", + "resource.customer-journey-canvas.title": "Customer Journey Canvas", + "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", + "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", + "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", "resource.customer-journey-canvas.steps.3": "Mapear as etapas do percurso com entradas/saídas", "resource.customer-journey-canvas.steps.4": "Identificar os problemas dos clientes", "resource.customer-journey-canvas.steps.5": "Resumir os ganhos dos clientes", "resource.customer-journey-canvas.steps.6": "Definir os inputs necessários e os outputs resultantes", "resource.customer-journey-canvas.steps.7": "Definir interações API para cada etapa", - "resource.customer-journey-canvas.tips": "Iterar com o contributo da equipa para aperfeiçoar as etapas", - "resource.customer-journey-canvas.tips.1": "Utilize os resultados deste quadro para informar outros quadros, como o quadro de proposta de valor da API", + "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.event-canvas.title": "Canvas de Eventos", "resource.event-canvas.description": "Conceber APIs orientadas para eventos, definindo eventos, accionadores e lógica de processamento.", "resource.event-canvas.outcomes": "Arquitetura orientada para eventos definida", @@ -542,56 +542,46 @@ "resource.api-testing-best-practices.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.", "resource.apiops-CI-CD-for-apis.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.", "resource.api-audit-checklist.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.", - "resource.automation-opportunity-canvas.title": "Canvas de Hipótese de Automação", - "resource.automation-opportunity-canvas.description": "A compact primary canvas for linking optional supporting evidence to a testable automation hypothesis and validation decision.", - "resource.automation-opportunity-canvas.outcomes": "Testable automation hypothesis", - "resource.automation-opportunity-canvas.outcomes.1": "Supporting evidence, scope, assumptions, and validation experiment linked without duplicating other canvases", - "resource.automation-opportunity-canvas.outcomes.2": "Evidence-based decision to proceed, revise, redesign the process, or reject", - "resource.automation-opportunity-canvas.steps": "State the automation hypothesis and reference Journey, Value Proposition, Domain, Business Impact, Capacity, or other evidence only where relevant.", - "resource.automation-opportunity-canvas.steps.1": "Define the automation scope, out-of-scope work, and initial implementation hypothesis without making an architecture decision.", - "resource.automation-opportunity-canvas.steps.2": "Identify critical assumptions, design the smallest useful validation experiment, and record the decision after reviewing evidence.", - "resource.automation-opportunity-canvas.tips": "Treat Customer Journey, Capability Value Proposition, Domain, Business Impact, and Capacity as optional supporting evidence, not required outputs for every automation opportunity.", - "resource.automation-opportunity-canvas.tips.1": "Stop, narrow, or redesign weak opportunities before implementation choices become locked.", - "resource.human-automation-responsibility-canvas.title": "Human-Automation Responsibility Canvas", - "resource.human-automation-responsibility-canvas.description": "A canvas for creating the initial allocation of what should be performed by people, rules, workflows, agents, systems, APIs, or UI automation.", - "resource.human-automation-responsibility-canvas.outcomes": "Clear human and automation responsibilities", - "resource.human-automation-responsibility-canvas.outcomes.1": "Oversight, escalation, and audit evidence defined by process step", - "resource.human-automation-responsibility-canvas.outcomes.2": "Implementation mechanisms selected without assuming every step should be automated", - "resource.human-automation-responsibility-canvas.steps": "List the target process steps and current handoffs.", - "resource.human-automation-responsibility-canvas.steps.1": "Assign each step to people, rules, workflows, agents, systems, APIs, UI automation, or a hybrid responsibility.", - "resource.human-automation-responsibility-canvas.steps.2": "Define oversight, escalation, and evidence for each step so later architecture and workflow design can validate and refine the allocation.", - "resource.human-automation-responsibility-canvas.tips": "Keep accountability visible even when execution is automated.", - "resource.human-automation-responsibility-canvas.tips.1": "Revisit this canvas later only to validate architecture assumptions or refine workflow-level handoffs and exceptions.", + "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", + "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", + "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", + "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "A canvas for designing the automation sequence, states, data, triggers, decisions, system interactions, failure paths, evidence, monitoring, and recovery.", - "resource.automation-workflow-canvas.outcomes": "Testable automation workflow design", - "resource.automation-workflow-canvas.outcomes.1": "Triggers, stages, states, decisions, data, interactions, handoffs, exceptions, and recovery paths defined", - "resource.automation-workflow-canvas.outcomes.2": "Operational evidence and monitoring points identified before delivery", - "resource.automation-workflow-canvas.steps": "Separate the target process from the technical workflow.", - "resource.automation-workflow-canvas.steps.1": "Map triggers, inputs, stages, states, decisions, automation actions, system interactions, data sources, handoffs, outputs, and exceptions.", - "resource.automation-workflow-canvas.steps.2": "Define retries, timeouts, duplicate prevention, audit evidence, monitoring points, and recovery paths.", - "resource.automation-workflow-canvas.tips": "Treat exceptions and manual recovery as part of the design, not an afterthought.", - "resource.automation-workflow-canvas.tips.1": "Revisit the Human-Automation Responsibility Canvas separately to refine responsibility allocation, oversight, escalation, and evidence for the workflow stages now being designed.", + "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", + "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", + "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "A canvas for comparing and justifying alternative implementation mechanisms for an automation solution.", - "resource.automation-architecture-decision-canvas.outcomes": "Justified automation architecture and implementation approach", - "resource.automation-architecture-decision-canvas.outcomes.1": "Candidate mechanisms compared on quality, risk, cost, skills, and operational fit", - "resource.automation-architecture-decision-canvas.outcomes.2": "Hybrid solution decisions documented", - "resource.automation-architecture-decision-canvas.steps": "Marque cada mecanismo candidato como considerado, selecionado, rejeitado ou não relevante antes de comparar as opções viáveis.", - "resource.automation-architecture-decision-canvas.steps.1": "Evaluate feasibility, reliability, security, maintainability, latency, scalability, cost, vendor dependency, testability, observability, recoverability, skills, and architectural fit.", - "resource.automation-architecture-decision-canvas.steps.2": "Document the preferred hybrid approach, rationale, risks, and open assumptions.", - "resource.automation-architecture-decision-canvas.tips": "Do not force every mechanism into the solution; make irrelevant candidates explicit and compare only viable options.", - "resource.automation-architecture-decision-canvas.tips.1": "Choose UI automation only when more stable system or integration paths are insufficient.", - "resource.automation-readiness-operations-canvas.title": "Canvas de Prontidão e Operações da Automação", - "resource.automation-readiness-operations-canvas.description": "A canvas for preparing the operating model for a safely released, supported, monitored, and recoverable automation.", - "resource.automation-readiness-operations-canvas.outcomes": "Documented automation operating model", - "resource.automation-readiness-operations-canvas.outcomes.1": "Ownership, permissions, environments, evidence, monitoring, support, fallback, rollback, and risks prepared", - "resource.automation-readiness-operations-canvas.outcomes.2": "Release readiness status and improvement backlog ready for readiness review and post-release learning", - "resource.automation-readiness-operations-canvas.steps": "Prepare business owner, operational owner, affected users, permissions, credentials, environments, and documentation.", - "resource.automation-readiness-operations-canvas.steps.1": "Prepare test evidence, exception handling, monitoring, support, manual fallback, rollback, and known risks.", - "resource.automation-readiness-operations-canvas.steps.2": "Registe o estado de prontidão para lançamento e o backlog de melhoria sem tomar a decisão formal de prontidão.", - "resource.automation-readiness-operations-canvas.tips": "Use isto durante Delivery & Operations para preparar evidências; use a checklist de prontidão da automação para a decisão formal de lançamento.", - "resource.automation-readiness-operations-canvas.tips.1": "Make manual fallback and operational ownership explicit before production use.", + "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", + "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", + "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", + "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", + "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", + "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", @@ -613,46 +603,46 @@ "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", "resource.automation-monitoring-value-metrics.tips": "A monitorização transforma evidências operacionais, de utilizador, risco e valor em decisões de ciclo de vida e num backlog de melhoria.", "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Canvas de Hipótese de Capacidade de Integração", - "resource.integration-capability-hypothesis-canvas.description": "Canvas de Hipótese de Capacidade de Integração apoia o planeamento, decisão, entrega, publicação ou melhoria de uma capacidade de integração reutilizável.", - "resource.integration-capability-hypothesis-canvas.outcomes": "Base de trabalho de integração documentada", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Decisões, responsabilidades, evidências e restrições principais documentadas", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "Próximos passos, riscos e pontos em aberto visíveis para o trabalho de integração", - "resource.integration-capability-hypothesis-canvas.steps": "Clarifique objetivo, partes envolvidas, escopo e evidências relevantes.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Documente decisões, condições, responsabilidades e artefactos necessários.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Use os resultados no desenho, entrega, prontidão, publicação ou melhoria.", - "resource.integration-capability-hypothesis-canvas.tips": "Adapte este recurso ao estilo de integração escolhido.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Inclua produtores, consumidores, plataforma, operações, segurança, compliance e negócio.", - "resource.integration-consumer-provider-requirements-canvas.title": "Canvas de Requisitos do Consumidor e Provider de Integração", - "resource.integration-consumer-provider-requirements-canvas.description": "Canvas de Requisitos do Consumidor e Provider de Integração apoia o planeamento, decisão, entrega, publicação ou melhoria de uma capacidade de integração reutilizável.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "Base de trabalho de integração documentada", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Decisões, responsabilidades, evidências e restrições principais documentadas", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "Próximos passos, riscos e pontos em aberto visíveis para o trabalho de integração", - "resource.integration-consumer-provider-requirements-canvas.steps": "Clarifique objetivo, partes envolvidas, escopo e evidências relevantes.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Documente decisões, condições, responsabilidades e artefactos necessários.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Use os resultados no desenho, entrega, prontidão, publicação ou melhoria.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Adapte este recurso ao estilo de integração escolhido.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Inclua produtores, consumidores, plataforma, operações, segurança, compliance e negócio.", - "resource.integration-architecture-decision-canvas.title": "Canvas de Decisão de Arquitetura de Integração", - "resource.integration-architecture-decision-canvas.description": "Canvas de Decisão de Arquitetura de Integração apoia o planeamento, decisão, entrega, publicação ou melhoria de uma capacidade de integração reutilizável.", - "resource.integration-architecture-decision-canvas.outcomes": "Base de trabalho de integração documentada", - "resource.integration-architecture-decision-canvas.outcomes.1": "Estilos candidatos comparados com estado, e estilo ou híbrido selecionado registado", - "resource.integration-architecture-decision-canvas.outcomes.2": "Próximos passos, riscos e pontos em aberto visíveis para o trabalho de integração", - "resource.integration-architecture-decision-canvas.steps": "Use o controlo de estado do candidato para marcar cada estilo como considerado, selecionado, rejeitado ou não relevante.", - "resource.integration-architecture-decision-canvas.steps.1": "Documente decisões, condições, responsabilidades e artefactos necessários.", - "resource.integration-architecture-decision-canvas.steps.2": "Use os resultados no desenho, entrega, prontidão, publicação ou melhoria.", - "resource.integration-architecture-decision-canvas.tips": "Adapte este recurso ao estilo de integração escolhido.", - "resource.integration-architecture-decision-canvas.tips.1": "Inclua produtores, consumidores, plataforma, operações, segurança, compliance e negócio.", - "resource.integration-readiness-operations-canvas.title": "Canvas de Prontidão e Operações da Integração", - "resource.integration-readiness-operations-canvas.description": "Canvas de Prontidão e Operações da Integração apoia o planeamento, decisão, entrega, publicação ou melhoria de uma capacidade de integração reutilizável.", - "resource.integration-readiness-operations-canvas.outcomes": "Base de trabalho de integração documentada", - "resource.integration-readiness-operations-canvas.outcomes.1": "Decisões, responsabilidades, evidências e restrições principais documentadas", - "resource.integration-readiness-operations-canvas.outcomes.2": "Próximos passos, riscos e pontos em aberto visíveis para o trabalho de integração", - "resource.integration-readiness-operations-canvas.steps": "Clarifique objetivo, partes envolvidas, escopo e evidências relevantes.", - "resource.integration-readiness-operations-canvas.steps.1": "Documente decisões, condições, responsabilidades e artefactos necessários.", - "resource.integration-readiness-operations-canvas.steps.2": "Use os resultados no desenho, entrega, prontidão, publicação ou melhoria.", - "resource.integration-readiness-operations-canvas.tips": "Adapte este recurso ao estilo de integração escolhido.", - "resource.integration-readiness-operations-canvas.tips.1": "Inclua produtores, consumidores, plataforma, operações, segurança, compliance e negócio.", + "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", + "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", + "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", + "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", + "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", + "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", + "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", + "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", + "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", + "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.integration-consumer-onboarding-guide.title": "Guia de onboarding de consumidores de integração", "resource.integration-consumer-onboarding-guide.description": "Guia de onboarding de consumidores de integração apoia o planeamento, decisão, entrega, publicação ou melhoria de uma capacidade de integração reutilizável.", "resource.integration-consumer-onboarding-guide.outcomes": "Base de trabalho de integração documentada", @@ -823,66 +813,66 @@ "resource.integration-lifecycle-management-guide.steps.2": "Use os resultados no desenho, entrega, prontidão, publicação ou melhoria.", "resource.integration-lifecycle-management-guide.tips": "Adapte este recurso ao estilo de integração escolhido.", "resource.integration-lifecycle-management-guide.tips.1": "Inclua produtores, consumidores, plataforma, operações, segurança, compliance e negócio.", - "resource.integration-solution-design-canvas.title": "Canvas de Desenho da Solução de Integração", - "resource.integration-solution-design-canvas.description": "Canvas de resumo para decisões de desenho de integração entre estilos, incluindo estilo, produtores, consumidores, contratos, esquemas, mapeamentos, padrão de entrega, segurança, erros, retry, replay, correlação, reconciliação, observabilidade e versionamento.", - "resource.integration-solution-design-canvas.outcomes": "Resumo completo do desenho da solução de integração", - "resource.integration-solution-design-canvas.outcomes.1": "Decisões de contrato, esquema, mapeamento, entrega, segurança, recuperação e observabilidade documentadas", - "resource.integration-solution-design-canvas.outcomes.2": "Desenho rastreável à decisão de arquitetura e aos requisitos de consumidor/provider", - "resource.integration-solution-design-canvas.steps": "Comece pelo estilo de arquitetura ou híbrido selecionado.", - "resource.integration-solution-design-canvas.steps.1": "Documente contratos, esquemas, mapeamentos, transformações, padrão de entrega, identidade, segurança, erros, retry, replay, correlação, reconciliação, observabilidade e versionamento.", - "resource.integration-solution-design-canvas.steps.2": "Use Interaction Canvas e recursos específicos do estilo apenas quando for necessário detalhe adicional de desenho.", - "resource.integration-solution-design-canvas.tips": "Use isto como artefacto principal de Integration Solution Design.", - "resource.integration-solution-design-canvas.tips.1": "Cubra orquestração de workflow, B2B/EDI, webhooks, modelos de dados canónicos, ficheiros, streams, mensageria, produtos de dados, APIs e connectors quando relevante.", - "resource.capability-hypothesis-canvas.title": "Canvas de Hipótese de Capacidade", - "resource.capability-hypothesis-canvas.description": "Canvas de Hipótese de Capacidade apoia a etapa de capacidade correspondente com decisões, evidências, responsabilidades, riscos e próximos passos específicos.", - "resource.capability-hypothesis-canvas.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "resource.capability-hypothesis-canvas.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "resource.capability-hypothesis-canvas.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "resource.capability-hypothesis-canvas.steps": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "resource.capability-hypothesis-canvas.steps.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "resource.capability-hypothesis-canvas.steps.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "resource.capability-hypothesis-canvas.tips": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "resource.capability-hypothesis-canvas.tips.1": "Mantenha canvases de apoio como evidência opcional, não como trabalho obrigatório.", - "resource.capability-consumer-producer-requirements-canvas.title": "Canvas de Requisitos do Consumidor e Produtor", - "resource.capability-consumer-producer-requirements-canvas.description": "Canvas de Requisitos do Consumidor e Produtor apoia a etapa de capacidade correspondente com decisões, evidências, responsabilidades, riscos e próximos passos específicos.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "resource.capability-consumer-producer-requirements-canvas.steps": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Mantenha canvases de apoio como evidência opcional, não como trabalho obrigatório.", - "resource.capability-architecture-decision-canvas.title": "Canvas de Decisão de Arquitetura de Capacidade", - "resource.capability-architecture-decision-canvas.description": "Canvas de Decisão de Arquitetura de Capacidade apoia a etapa de capacidade correspondente com decisões, evidências, responsabilidades, riscos e próximos passos específicos.", - "resource.capability-architecture-decision-canvas.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "resource.capability-architecture-decision-canvas.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "resource.capability-architecture-decision-canvas.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "resource.capability-architecture-decision-canvas.steps": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "resource.capability-architecture-decision-canvas.steps.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "resource.capability-architecture-decision-canvas.steps.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "resource.capability-architecture-decision-canvas.tips": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "resource.capability-architecture-decision-canvas.tips.1": "Mantenha canvases de apoio como evidência opcional, não como trabalho obrigatório.", - "resource.capability-solution-design-canvas.title": "Canvas de Desenho da Solução de Capacidade", - "resource.capability-solution-design-canvas.description": "Canvas de Desenho da Solução de Capacidade apoia a etapa de capacidade correspondente com decisões, evidências, responsabilidades, riscos e próximos passos específicos.", - "resource.capability-solution-design-canvas.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "resource.capability-solution-design-canvas.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "resource.capability-solution-design-canvas.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "resource.capability-solution-design-canvas.steps": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "resource.capability-solution-design-canvas.steps.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "resource.capability-solution-design-canvas.steps.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "resource.capability-solution-design-canvas.tips": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "resource.capability-solution-design-canvas.tips.1": "Mantenha canvases de apoio como evidência opcional, não como trabalho obrigatório.", - "resource.capability-readiness-operations-canvas.title": "Canvas de Prontidão e Operações da Capacidade", - "resource.capability-readiness-operations-canvas.description": "Canvas de Prontidão e Operações da Capacidade apoia a etapa de capacidade correspondente com decisões, evidências, responsabilidades, riscos e próximos passos específicos.", - "resource.capability-readiness-operations-canvas.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "resource.capability-readiness-operations-canvas.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "resource.capability-readiness-operations-canvas.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "resource.capability-readiness-operations-canvas.steps": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "resource.capability-readiness-operations-canvas.steps.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "resource.capability-readiness-operations-canvas.steps.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "resource.capability-readiness-operations-canvas.tips": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "resource.capability-readiness-operations-canvas.tips.1": "Mantenha canvases de apoio como evidência opcional, não como trabalho obrigatório.", + "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", + "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", + "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", + "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", + "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", + "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", + "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", + "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", + "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", + "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", + "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", + "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", + "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", + "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", + "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", + "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", + "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", + "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", + "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", + "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", + "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", "resource.capability-consumer-onboarding-guide.title": "Guia de onboarding de consumidores da capacidade", "resource.capability-consumer-onboarding-guide.description": "Guia de onboarding de consumidores da capacidade apoia a etapa de capacidade correspondente com decisões, evidências, responsabilidades, riscos e próximos passos específicos.", "resource.capability-consumer-onboarding-guide.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", diff --git a/src/data/method/resources.json b/src/data/method/resources.json index 2a4c9ad..03175ca 100644 --- a/src/data/method/resources.json +++ b/src/data/method/resources.json @@ -1408,32 +1408,6 @@ }, "category": "canvas" }, - { - "id": "humanAutomationResponsibilityCanvas", - "title": "resource.human-automation-responsibility-canvas.title", - "slug": "resources/human-automation-responsibility-canvas", - "icon": "dashboard-outline", - "order": 190, - "description": "resource.human-automation-responsibility-canvas.description", - "canvas": "humanAutomationResponsibilityCanvas", - "outcomes": [ - "resource.human-automation-responsibility-canvas.outcomes", - "resource.human-automation-responsibility-canvas.outcomes.1", - "resource.human-automation-responsibility-canvas.outcomes.2" - ], - "how_it_works": { - "steps": [ - "resource.human-automation-responsibility-canvas.steps", - "resource.human-automation-responsibility-canvas.steps.1", - "resource.human-automation-responsibility-canvas.steps.2" - ], - "tips": [ - "resource.human-automation-responsibility-canvas.tips", - "resource.human-automation-responsibility-canvas.tips.1" - ] - }, - "category": "canvas" - }, { "id": "automationWorkflowCanvas", "title": "resource.automation-workflow-canvas.title", diff --git a/src/data/method/station-stakeholders.json b/src/data/method/station-stakeholders.json index 189b6bf..f2a245a 100644 --- a/src/data/method/station-stakeholders.json +++ b/src/data/method/station-stakeholders.json @@ -1,7 +1,7 @@ { "stationStakeholdersByCycle": { "capability-productization-cycle": { - "capability-strategy": [ + "api-product-strategy": [ { "stakeholder": "capability-owner", "involvement": "lead", @@ -37,7 +37,7 @@ "involvement": "consulted" } ], - "capability-consumer-producer-requirements": [ + "api-consumer-experience": [ { "stakeholder": "customer-specialist", "involvement": "lead", @@ -73,7 +73,7 @@ "involvement": "consulted" } ], - "capability-architecture-platform-decisions": [ + "api-platform-architecture": [ { "stakeholder": "platform-architect", "involvement": "lead", @@ -113,7 +113,7 @@ "involvement": "consulted" } ], - "capability-solution-interaction-design": [ + "api-design": [ { "stakeholder": "api-designer", "involvement": "lead", @@ -153,7 +153,7 @@ "involvement": "consulted" } ], - "capability-delivery-operations": [ + "api-delivery": [ { "stakeholder": "api-engineer", "involvement": "lead", @@ -189,7 +189,7 @@ "involvement": "consulted" } ], - "capability-readiness-assurance": [ + "api-audit": [ { "stakeholder": "governance-specialist", "involvement": "lead", @@ -229,7 +229,7 @@ "involvement": "consulted" } ], - "capability-publishing-enablement": [ + "api-publishing": [ { "stakeholder": "capability-owner", "involvement": "lead", @@ -265,7 +265,7 @@ "involvement": "consulted" } ], - "capability-monitoring-improvement": [ + "monitoring-and-improving": [ { "stakeholder": "capability-owner", "involvement": "lead", @@ -643,7 +643,7 @@ ] }, "integration-productization-cycle": { - "integration-capability-strategy": [ + "api-product-strategy": [ { "stakeholder": "integration-architect", "involvement": "lead", @@ -679,7 +679,7 @@ "involvement": "consulted" } ], - "integration-consumer-requirements-onboarding": [ + "api-consumer-experience": [ { "stakeholder": "api-consumer-specialist", "involvement": "lead", @@ -715,7 +715,7 @@ "involvement": "consulted" } ], - "integration-architecture-platform-decisions": [ + "api-platform-architecture": [ { "stakeholder": "platform-architect", "involvement": "lead", @@ -759,7 +759,7 @@ "involvement": "consulted" } ], - "integration-solution-design": [ + "api-design": [ { "stakeholder": "integration-architect", "involvement": "lead", @@ -799,7 +799,7 @@ "involvement": "consulted" } ], - "integration-delivery-operations": [ + "api-delivery": [ { "stakeholder": "api-engineer", "involvement": "lead", @@ -839,7 +839,7 @@ "involvement": "consulted" } ], - "integration-readiness-assurance": [ + "api-audit": [ { "stakeholder": "governance-specialist", "involvement": "lead", @@ -879,7 +879,7 @@ "involvement": "consulted" } ], - "integration-publishing-enablement": [ + "api-publishing": [ { "stakeholder": "integration-architect", "involvement": "lead", @@ -919,7 +919,7 @@ "involvement": "consulted" } ], - "integration-monitoring-improvement": [ + "monitoring-and-improving": [ { "stakeholder": "integration-architect", "involvement": "lead", @@ -1020,13 +1020,7 @@ "api-consumer-experience": [ { "stakeholder": "process-owner", - "involvement": "lead", - "responsibilities": [ - { - "resource": "humanAutomationResponsibilityCanvas", - "role": "suggested-answer-owner" - } - ] + "involvement": "lead" }, { "stakeholder": "automation-owner", @@ -1037,7 +1031,7 @@ "involvement": "core", "responsibilities": [ { - "resource": "userOperatorExperienceRequirementsCanvas", + "resource": "consumerExperienceRequirementsCanvas", "role": "suggested-answer-owner" } ] From fce15d4a80bae68bc392fce734faa369657d520d Mon Sep 17 00:00:00 2001 From: Marjukka Niinioja Date: Wed, 5 Aug 2026 18:00:41 +0300 Subject: [PATCH 2/3] fixed inconsistencies in stations and criteria, cleaned up localizations --- scripts/test-method-content-integrity.mjs | 49 +- scripts/test-method-stakeholders.mjs | 2 +- src/data/method/de/labels.criteria.json | 10 +- src/data/method/de/labels.cycles.json | 44 +- src/data/method/de/labels.resources.json | 392 +++++------ src/data/method/de/labels.stakeholders.json | 6 +- src/data/method/de/labels.stations.json | 200 +----- src/data/method/en/labels.stations.json | 208 +----- src/data/method/fi/labels.criteria.json | 10 +- src/data/method/fi/labels.cycles.json | 44 +- src/data/method/fi/labels.resources.json | 376 +++++----- src/data/method/fi/labels.stations.json | 214 +----- src/data/method/fr/labels.criteria.json | 10 +- src/data/method/fr/labels.cycles.json | 44 +- src/data/method/fr/labels.resources.json | 398 +++++------ src/data/method/fr/labels.stations.json | 214 +----- src/data/method/pt/labels.criteria.json | 10 +- src/data/method/pt/labels.cycles.json | 30 +- src/data/method/pt/labels.resources.json | 376 +++++----- src/data/method/pt/labels.stations.json | 310 +------- src/data/method/station-criteria.json | 314 +++++---- src/data/method/stations.json | 738 -------------------- src/lib/method-engine.js | 12 +- src/schemas/station-criteria.schema.json | 25 +- 24 files changed, 1142 insertions(+), 2894 deletions(-) diff --git a/scripts/test-method-content-integrity.mjs b/scripts/test-method-content-integrity.mjs index be4d38c..108fca3 100644 --- a/scripts/test-method-content-integrity.mjs +++ b/scripts/test-method-content-integrity.mjs @@ -29,6 +29,12 @@ const findings = []; const warnings = []; const lifecycleStages = new Set(["strategy", "architecture", "design", "delivery", "publishing", "improving"]); +function resolveStationCriteria(stationId, cycleId) { + return stationCriteriaJson.byCycle?.[cycleId]?.[stationId] + || stationCriteriaJson.default?.[stationId] + || []; +} + function collectMatchingStringValues(node, pattern, results = new Set()) { if (typeof node === "string") { if (pattern.test(node)) { @@ -118,10 +124,10 @@ for (const station of stationGroups) { findings.push(`Core station ${station.id} is missing a valid lifecycleStage.`); } - const expectedCriteria = stationCriteriaJson[station.id] || []; + const expectedCriteria = stationCriteriaJson.default?.[station.id] || []; const actualCriteria = station.stationCriteria || []; if (JSON.stringify(actualCriteria) !== JSON.stringify(expectedCriteria)) { - findings.push(`Core station ${station.id} stationCriteria does not match station-criteria.json.`); + findings.push(`Core station ${station.id} stationCriteria does not match station-criteria.json default criteria.`); } if (!Array.isArray(station.expectedEvidenceTags) || station.expectedEvidenceTags.length === 0) { @@ -264,6 +270,45 @@ for (const cycle of cyclesJson.cycles?.items || []) { } } + const cycleCriteriaMap = stationCriteriaJson.byCycle?.[cycle.id] || {}; + for (const [stationId, criterionIds] of Object.entries(cycleCriteriaMap)) { + if (!knownStationIds.has(stationId)) { + findings.push(`Cycle ${cycle.id} station criteria references unknown station "${stationId}".`); + } + if (!(cycle.stations || []).includes(stationId)) { + findings.push(`Cycle ${cycle.id} station criteria references station outside the cycle: ${stationId}.`); + } + for (const criterionId of criterionIds || []) { + if (!knownCriteriaIds.has(criterionId)) { + findings.push(`Cycle ${cycle.id} station criteria for "${stationId}" references unknown criterion "${criterionId}".`); + } + } + } + + for (const stationId of cycle.stations || []) { + const criterionIds = resolveStationCriteria(stationId, cycle.id); + if (!Array.isArray(criterionIds) || criterionIds.length === 0) { + findings.push(`Cycle ${cycle.id} station "${stationId}" has no station criteria.`); + } + } + +} + +for (const [stationId, criterionIds] of Object.entries(stationCriteriaJson.default || {})) { + if (!knownStationIds.has(stationId)) { + findings.push(`Default station criteria references unknown station "${stationId}".`); + } + for (const criterionId of criterionIds || []) { + if (!knownCriteriaIds.has(criterionId)) { + findings.push(`Default station criteria for "${stationId}" references unknown criterion "${criterionId}".`); + } + } +} + +for (const cycleId of Object.keys(stationCriteriaJson.byCycle || {})) { + if (!knownCycleIds.has(cycleId)) { + findings.push(`Station criteria references unknown cycle "${cycleId}".`); + } } const stationsUsedInLines = new Set( diff --git a/scripts/test-method-stakeholders.mjs b/scripts/test-method-stakeholders.mjs index 4609609..a7a5661 100644 --- a/scripts/test-method-stakeholders.mjs +++ b/scripts/test-method-stakeholders.mjs @@ -74,7 +74,7 @@ const architectureData = methodEngine.buildStationResourceData("api-platform-arc assert.ok(architectureData.stakeholders.some((entry) => entry.id === "security-specialist"), "Expected api-platform-architecture to include security-specialist."); assert.ok(architectureData.stakeholders.some((entry) => entry.id === "compliance-specialist"), "Expected api-platform-architecture to include compliance-specialist."); -const capabilityStrategyData = methodEngine.buildStationResourceData("capability-strategy", "en", methodEngine.DEFAULT_STYLE, "capability-productization-cycle"); +const capabilityStrategyData = methodEngine.buildStationResourceData("api-product-strategy", "en", methodEngine.DEFAULT_STYLE, "capability-productization-cycle"); assert.ok( capabilityStrategyData.steps.some((entry) => entry.resourceId === "capabilityHypothesisCanvas"), "Expected capability cycle strategy resources to use capability hypothesis canvas." diff --git a/src/data/method/de/labels.criteria.json b/src/data/method/de/labels.criteria.json index d08d1f4..7640bb9 100644 --- a/src/data/method/de/labels.criteria.json +++ b/src/data/method/de/labels.criteria.json @@ -23,11 +23,11 @@ "criterion.api-documentation-ready": "Nutzerorientierte Dokumentation und Onboarding-Materialien sind bereit.", "criterion.consumer-support-ready": "Onboarding-, Support- und Kommunikationsprozesse für Nutzer sind bereit.", "criterion.legal-compliance-clear": "Rechtliche, Datenschutz- und Compliance-Anforderungen für Veröffentlichung oder Release sind definiert und verstanden.", - "criterion.automation-opportunity-evidence-ready": "The automation hypothesis has enough referenced evidence about expected outcome, scope, initial implementation assumptions, critical risks, validation experiment, thresholds, and decision to determine whether it should proceed.", - "criterion.automation-owner-confirmed": "Ownership is clear for the automation opportunity, process decisions, PoC validation, risks, and lifecycle outcomes.", - "criterion.automation-architecture-and-controls-validated": "The selected automation architecture, implementation mechanisms, human controls, security constraints, and recovery approach have been validated with the relevant stakeholders.", - "criterion.automation-operational-readiness-confirmed": "The automation has evidence for functional correctness, permissions, exception handling, oversight, monitoring, support, rollback, and operational ownership.", - "criterion.automation-value-monitoring-ready": "Automation performance, process outcomes, risk signals, manual interventions, incidents, and realized benefits can be monitored and used to prioritize improvements.", + "criterion.automation-opportunity-evidence-ready": "Die Automatisierungshypothese verfügt über ausreichend referenzierte Nachweise zum erwarteten Ergebnis, Umfang, zu anfänglichen Umsetzungsannahmen, kritischen Risiken, Validierungsexperiment, Schwellenwerten und zur Entscheidung, um zu bestimmen, ob sie weiterverfolgt werden soll.", + "criterion.automation-owner-confirmed": "Die Verantwortlichkeit für die Automatisierungschance, Prozessentscheidungen, PoC-Validierung, Risiken und Lebenszyklusergebnisse ist geklärt.", + "criterion.automation-architecture-and-controls-validated": "Die ausgewählte Automatisierungsarchitektur, Umsetzungsmechanismen, menschlichen Kontrollen, Sicherheitsbeschränkungen und der Wiederherstellungsansatz wurden mit den relevanten Stakeholdern validiert.", + "criterion.automation-operational-readiness-confirmed": "Für die Automatisierung liegen Nachweise zu funktionaler Korrektheit, Berechtigungen, Ausnahmebehandlung, Aufsicht, Monitoring, Support, Rollback und operativer Verantwortlichkeit vor.", + "criterion.automation-value-monitoring-ready": "Automatisierungsleistung, Prozessergebnisse, Risikosignale, manuelle Eingriffe, Vorfälle und realisierte Vorteile können überwacht und zur Priorisierung von Verbesserungen genutzt werden.", "criterion.integration-readiness-confirmed": "Integrationsverträge, Schemas, Mappings, Testnachweise, Umgebungen, Berechtigungen, Credentials, Monitoring, Support, Replay, Abstimmung, Fallback, Wiederherstellung, Risiken und Ownership wurden für die Release Readiness geprüft.", "criterion.integration-published-for-reuse": "Die Integrationsfähigkeit ist auffindbar und enthält veröffentlichte Ownership, Lifecycle-Status, Verträge, Schemas, Serviceerwartungen, Zugriffs- und Onboarding-Pfade, Support, Versionierung und Feedbackkanäle.", "criterion.capability-readiness-confirmed": "Capability Design, Service Definition, Testnachweise, Betriebsmodell, Berechtigungen, Monitoring, Support, Fallback, Lifecycle-Regelungen, Risiken und Ownership wurden für Release Readiness geprüft.", diff --git a/src/data/method/de/labels.cycles.json b/src/data/method/de/labels.cycles.json index 9b12c3c..cea409a 100644 --- a/src/data/method/de/labels.cycles.json +++ b/src/data/method/de/labels.cycles.json @@ -12,7 +12,7 @@ "cycle.integration-productization-cycle.purpose": "Unterstuetzt das Design wiederverwendbarer Integrations-Capabilities, bevor ein API-, Event-, Datei-, Stream-, Datenprodukt-, direkte Integrations- oder hybrider Implementierungsstil gewaehlt wird.", "cycle.station.capability-strategy": "Capability-Strategie", "cycle.station.api-product-strategy": "API-Produktstrategie", - "cycle.station.api-consumer-experience": "API Consumer Experience", + "cycle.station.api-consumer-experience": "API-Nutzererlebnis", "cycle.station.api-platform-architecture": "API-Plattformarchitektur", "cycle.station.api-design": "API-Design", "cycle.station.api-delivery": "API-Bereitstellung", @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "API-Veröffentlichung", "cycle.station.monitoring-and-improving": "API-Monitoring & Verbesserung", "cycle.station.integration-capability-strategy": "Integrations-Capability-Strategie", - "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", + "cycle.station.integration-consumer-requirements-onboarding": "Verpflichtungen von Integrationsnutzern und -anbietern", "cycle.station.integration-architecture-decision": "Integrationsarchitektur & Plattformentscheidungen", "cycle.station.integration-solution-design": "Integrationsdesign", "cycle.station.integration-delivery-operations": "Integrationsbereitstellung & Betrieb", @@ -47,7 +47,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Überwachen Sie API-Gesundheit, Adoption, Nutzerergebnisse, Zuverlässigkeit und Verbesserungsmöglichkeiten nach der Veröffentlichung.", "cycle.automation-cycle.title": "Automatisierungszyklus", "cycle.automation-cycle.description": "Ein Zyklus zum Auswählen, Entwerfen, Bereitstellen, Einführen und Verbessern von Automatisierungslösungen über Menschen, Regeln, Workflows, Agenten, Integrationen, UI-Automatisierung und Betrieb hinweg.", - "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", + "cycle.automation-cycle.purpose": "Teams von externen Kunden- und Fähigkeitsergebnissen zu einer validierten, gesteuerten und betreibbaren Automatisierungslösung führen.", "cycle.audience.automation-owners": "Automation Owner", "cycle.audience.process-owners": "Prozessverantwortliche", "cycle.audience.automation-teams": "Automatisierungsteams", @@ -57,33 +57,33 @@ "cycle.station.automation-readiness-review": "Automatisierungsbereitschaftsprüfung", "cycle.station.automation-enablement": "Automatisierungs-Rollout & Enablement", "cycle.station.automation-monitoring-improvement": "Automatisierungsmonitoring & Verbesserung", - "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", - "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", - "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", + "cycle.automation-cycle.station.api-product-strategy.description": "Beginnen Sie mit dem relevantesten externen Kunden. Nutzen Sie Nachweise aus Journey und Fähigkeitswert, um zu validieren, ob eine Automatisierungshypothese weiterverfolgt werden soll.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Klären Sie Prozess-, Erlebnis-, Domänen-, Service- und nichtfunktionale Anforderungen, die der spätere Workflow und die Architektur erfüllen müssen.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Nutzen Sie Auswirkungen, Standort, Kapazität und frühere Anforderungen, um den Umsetzungsansatz für die Automatisierung zu wählen und Begründung sowie verbleibende Risiken festzuhalten.", + "cycle.automation-cycle.station.api-design.description": "Entwerfen Sie den internen Workflow, der zur Erreichung der ausgewählten Kunden- und Fähigkeitsergebnisse benötigt wird, einschließlich Arbeitsverteilung, Kontrollen, Ausnahmen, Wiederherstellung, Nachweisen und Monitoring.", + "cycle.automation-cycle.station.api-delivery.description": "Bauen, konfigurieren, testen, versionieren und deployen Sie den ausgewählten Automatisierungspfad und bereiten Sie das Betriebsmodell vor, einschließlich Verantwortlichkeit, Umgebungen, Runbooks, Monitoring, Fallback, Rollback, Support und bekannter Risiken.", "cycle.automation-cycle.station.api-audit.description": "Nutzen Sie eine Readiness-Checkliste, um Nachweise zu prüfen und die Freigabeentscheidung festzuhalten: bereit, unter Bedingungen bereit, Nachbesserung erforderlich oder nicht genehmigt.", "cycle.automation-cycle.station.api-publishing.description": "Aktivieren und rollen Sie die Automatisierung sicher aus - mit Kommunikation, Schulung, Betriebsanweisungen, Supportwegen, Adoptionsmonitoring, Feedbackkanälen, phasenweisem Rollout sowie Pausen- und Rollback-Bedingungen.", - "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", - "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", + "cycle.automation-cycle.station.monitoring-and-improving.description": "Überwachen Sie tatsächliche Automatisierungsergebnisse, erfolgreiche und fehlgeschlagene Läufe, Ausnahmen, Wiederholungen, Eingriffe, Durchlaufzeit, Wartezeit, Kosten, Fehler, unsichere Aktionen, Einführung, Vertrauen, realisierten Nutzen und welche Hypothesenannahmen bestätigt oder verworfen wurden.", + "cycle.station.process-user-automation-requirements": "Prozess- und Erlebnisanforderungen", + "cycle.station.automation-architecture-platform-decision": "Entscheidung zu Automatisierungsarchitektur und Plattform", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Beginnen Sie mit Customer Journey, Fähigkeitswert und Tragfähigkeitsnachweisen und validieren Sie dann, ob die vorgeschlagene wiederverwendbare Integrationsfähigkeit weiterverfolgt werden soll.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Vereinbaren Sie Anbieter- und Nutzerverpflichtungen für Zugriff, Validierung, Service, Fehlerbehandlung, Wiederherstellung, Kompatibilität und Lebenszyklus.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Wählen Sie Integrationsarchitektur, Implementierungsstil und Plattformfähigkeiten unter Berücksichtigung von Randbedingungen und Governance.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Entwerfen Sie Integrationslösung, Verträge, Schemas, Datenstrukturen, Mappings sowie Interaktions- oder Liefermuster für den ausgewählten Stil.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Bauen, testen, deployen und betreiben Sie die Integrationsfähigkeit mit ausgewähltem Implementierungsstil und validiertem Vertrag.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Sichern Sie Integrations-Readiness, Governance, Qualität, Security, Compliance und operative Nachweise vor der Freigabe ab.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Veröffentlichen Sie die Integrationsfähigkeit, damit Teams sie finden, bewerten, Zugriff beantragen, onboarding durchführen, wiederverwenden und Support erhalten können.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Überwachen Sie Integrationszuverlässigkeit, Wiederverwendung, Incidents, Performance, Consumer-Ergebnisse und Verbesserungsbedarf.", - "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", - "cycle.station.capability-architecture-platform-decisions": "Capability Architecture & Platform Decisions", - "cycle.station.capability-solution-interaction-design": "Capability Solution & Interaction Design", - "cycle.station.capability-delivery-operations": "Capability Delivery & Operations", - "cycle.station.capability-readiness-assurance": "Capability Readiness Assurance", - "cycle.station.capability-publishing-enablement": "Capability Publishing & Enablement", - "cycle.station.capability-monitoring-improvement": "Capability Monitoring & Improvement", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", + "cycle.station.consumer-producer-service-requirements": "Verpflichtungen von Nutzern und Produzenten", + "cycle.station.capability-architecture-platform-decisions": "Entscheidungen zu Fähigkeitsarchitektur und Plattform", + "cycle.station.capability-solution-interaction-design": "Fähigkeitslösungs- und Interaktionsdesign", + "cycle.station.capability-delivery-operations": "Bereitstellung und Betrieb der Fähigkeit", + "cycle.station.capability-readiness-assurance": "Sicherstellung der Fähigkeitsbereitschaft", + "cycle.station.capability-publishing-enablement": "Veröffentlichung und Befähigung der Fähigkeit", + "cycle.station.capability-monitoring-improvement": "Monitoring und Verbesserung der Fähigkeit", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Beginnen Sie mit Customer Journey, Fähigkeitswert und Tragfähigkeitsnachweisen und validieren Sie dann, ob die vorgeschlagene wiederverwendbare digitale Fähigkeit weiterverfolgt werden soll.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Vereinbaren Sie gegenseitige Verpflichtungen von Owner, Produzenten und Nutzern für Zugriff, Service, Support, Änderungen und Lebenszyklus.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Capability Architecture & Platform Decisions: Führt die Definition wiederverwendbarer Fähigkeiten von Hypothese und Consumer-/Producer-Anforderungen über Architektur, Lösungsdesign, Lieferung, Readiness, Veröffentlichung und kontinuierliche Verbesserung.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Capability Solution & Interaction Design: Führt die Definition wiederverwendbarer Fähigkeiten von Hypothese und Consumer-/Producer-Anforderungen über Architektur, Lösungsdesign, Lieferung, Readiness, Veröffentlichung und kontinuierliche Verbesserung.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Capability Delivery & Operations: Führt die Definition wiederverwendbarer Fähigkeiten von Hypothese und Consumer-/Producer-Anforderungen über Architektur, Lösungsdesign, Lieferung, Readiness, Veröffentlichung und kontinuierliche Verbesserung.", diff --git a/src/data/method/de/labels.resources.json b/src/data/method/de/labels.resources.json index 5d53b52..1abbe5e 100644 --- a/src/data/method/de/labels.resources.json +++ b/src/data/method/de/labels.resources.json @@ -67,7 +67,7 @@ "resource.contract-first-design.title": "Contract-First Integration Design", "resource.contract-first-design.description": "Guidance for validating integration contracts before delivery, including OpenAPI, AsyncAPI, event schemas, message schemas, file schemas, data contracts, and interface specifications.", "resource.contract-first-design.outcomes": "Besseres Verständnis der Grundsätze der Vertragsgestaltung", - "resource.contract-first-design.steps": "Apply contract-first or design-first approaches to validate integration contracts before implementation.", + "resource.contract-first-design.steps": "Wenden Sie Contract-first- oder Design-first-Ansätze an, um Integrationsverträge vor der Umsetzung zu validieren.", "resource.contract-first-design.tips": "Passen Sie das Contract First Design für Ihre Domain an", "resource.cross-functional-collaboration-best-practices.title": "Best Practices für die funktionsübergreifende Zusammenarbeit", "resource.cross-functional-collaboration-best-practices.description": "Praktiken zur Erleichterung der Kommunikation und Abstimmung zwischen Geschäfts- und Technikerteams bei der Planung oder Bereitstellung von APIs.", @@ -79,7 +79,7 @@ "resource.data-privacy-guidelines.outcomes": "Besseres Verständnis der Grundsätze der Datenschutzleitlinien", "resource.data-privacy-guidelines.steps": "Gewährleistung des Datenschutzes für die Nutzer durch die Umsetzung von Datenschutzmaßnahmen wie Anonymisierung und Zugangskontrolle.", "resource.data-privacy-guidelines.tips": "Passen Sie die Datenschutzrichtlinien für Ihren Bereich an", - "resource.domain-canvas.title": "Domain Canvas", + "resource.domain-canvas.title": "Domänen-Canvas", "resource.domain-canvas.description": "Ein Modellierungstool zur Definition und Kommunikation der wichtigsten Entitäten und Beziehungen in Ihrer Domäne, das die semantische Konsistenz über APIs hinweg gewährleistet.", "resource.domain-canvas.outcomes": "Besseres Verständnis der Grundsätze des Domain Canvas", "resource.domain-canvas.steps": "Definieren Sie zentrale Entitäten, ihre Attribute und Beziehungen, um ein gemeinsames konzeptionelles Verständnis für alle APIs zu schaffen.", @@ -134,7 +134,7 @@ "resource.api-audit-checklist.outcomes": "Besseres Verständnis der Grundsätze der API Audit Checkliste", "resource.api-audit-checklist.steps": "Verwenden Sie die API Audit Checkliste, um sicherzustellen, dass der API-Entwurf die funktionalen und nicht-funktionalen Anforderungen erfüllt, einschließlich Sicherheit, Leistung und Compliance.", "resource.api-audit-checklist.tips": "Jeder Audit-Punkt verknüpft Lebenszyklus-Arbeitsschritte (Stationen), maßgebliche Richtlinien und unterstützende Nachweise, um einen klaren Überblick über die API-Bereitschaft zu bieten.", - "resource.api-business-model-canvas.title": "API Business Model Canvas", + "resource.api-business-model-canvas.title": "API-Geschäftsmodell-Canvas", "resource.api-business-model-canvas.description": "Strategische Bewertung der API-Geschäftsfähigkeit durch Zuordnung von Wertangeboten, Kundensegmenten und Schlüsselressourcen.", "resource.api-business-model-canvas.outcomes": "Klare Geschäftsstrategie für APIs", "resource.api-business-model-canvas.steps": "Fassen Sie das Wertversprechen der API zusammen", @@ -144,47 +144,47 @@ "resource.api-design-principles.outcomes": "Besseres Verständnis der API-Gestaltungsgrundsätze", "resource.api-design-principles.steps": "**Consumer-first design:** Wir beginnen jeden APIOps-Zyklus mit der Erfassung von Benutzerzielen und Fachbegriffen, damit APIs echte Probleme lösen.", "resource.api-design-principles.tips": "Anpassen der API-Entwurfsprinzipien für Ihre Domäne", - "resource.api-value-proposition-canvas.title": "API Value Proposition Canvas", + "resource.api-value-proposition-canvas.title": "API-Wertversprechen-Canvas", "resource.api-value-proposition-canvas.description": "Richten Sie API-Funktionen an den Bedürfnissen der Benutzer aus, indem Sie Aufgaben, Schmerzen und Gewinne auf API-Produkte abbilden.", "resource.api-value-proposition-canvas.outcomes": "Fokussierte Funktionsentwicklung", "resource.api-value-proposition-canvas.steps": "Aufgaben der Benutzerreise auflisten", "resource.api-value-proposition-canvas.tips": "Verwenden Sie den Input aus dem Customer Journey Canvas", - "resource.business-impact-canvas.title": "Business Impact Canvas", + "resource.business-impact-canvas.title": "Geschäftsauswirkungs-Canvas", "resource.business-impact-canvas.description": "Bewertet erwartete Vorteile sowie betriebliche, kundenbezogene, mitarbeiterbezogene, finanzielle, Compliance-, strategische, Risiko- und Nicht-Umsetzen-Auswirkungen, die Priorisierung und Entscheidungen prägen sollen.", "resource.business-impact-canvas.outcomes": "Dokumentierte Bewertung der Geschäftsauswirkungen", "resource.business-impact-canvas.steps": "Identifizieren Sie erwartete geschäftliche, kunden-, mitarbeiter-, qualitäts-, geschwindigkeits-, risiko-, Compliance- und strategische Vorteile.", "resource.business-impact-canvas.tips": "Nutzen Sie dies für Wert- und Konsequenznachweise, nicht nur für Risiko- und Resilienzanalyse.", - "resource.capacity-canvas.title": "Capacity Canvas", - "resource.capacity-canvas.description": "Quantify demand, load, timing, availability, and scaling needs for capabilities, automations, integrations, or services.", + "resource.capacity-canvas.title": "Kapazitäts-Canvas", + "resource.capacity-canvas.description": "Quantifizieren Sie Nachfrage, Last, Timing, Verfügbarkeit und Skalierungsbedarf für Fähigkeiten, Automatisierungen, Integrationen oder Services.", "resource.capacity-canvas.outcomes": "Anpassung der API-Kapazität an das Geschäftsvolumen", - "resource.capacity-canvas.steps": "Current Business Volumes: Quantify current business volumes and transaction rates.", - "resource.capacity-canvas.tips": "Use requirements canvases to capture what users need; use this canvas to quantify demand and inform scaling decisions.", - "resource.customer-journey-canvas.title": "Customer Journey Canvas", - "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", - "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", - "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.event-canvas.title": "Event Canvas", + "resource.capacity-canvas.steps": "Aktuelle Geschäftsvolumina: Quantifizieren Sie aktuelle Geschäftsvolumina und Transaktionsraten.", + "resource.capacity-canvas.tips": "Nutzen Sie Anforderungs-Canvases, um Nutzerbedarfe zu erfassen; nutzen Sie diesen Canvas, um Nachfrage zu quantifizieren und Skalierungsentscheidungen zu unterstützen.", + "resource.customer-journey-canvas.title": "Customer-Journey-Canvas", + "resource.customer-journey-canvas.description": "Welche Journey erlebt der relevanteste externe Kunde, und was sollte verbessert werden?", + "resource.customer-journey-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.customer-journey-canvas.steps": "Beginnen Sie mit dem relevantesten externen Kunden. Beschreiben Sie seine tatsächliche Journey, bevor Sie nach innen zu Fähigkeiten, internen Prozessen oder Umsetzungsentscheidungen verfolgen.", + "resource.customer-journey-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.event-canvas.title": "Event-Canvas", "resource.event-canvas.description": "Entwerfen Sie ereignisgesteuerte APIs, indem Sie Ereignisse, Auslöser und Verarbeitungslogik definieren.", "resource.event-canvas.outcomes": "Definierte ereignisgesteuerte Architektur", "resource.event-canvas.steps": "Identifizierung von Schlüsselereignissen im System", "resource.event-canvas.tips": "Verwendung von Ereignisschemata zur Standardisierung von Ereignisformaten", - "resource.graphql-canvas.title": "GraphQL Canvas", + "resource.graphql-canvas.title": "GraphQL-Canvas", "resource.graphql-canvas.description": "Entwerfen Sie GraphQL-APIs, indem Sie Typen, Abfragen, Mutationen und Abonnements definieren.", "resource.graphql-canvas.outcomes": "Strukturierter GraphQL-API-Entwurf", "resource.graphql-canvas.steps": "Welche Probleme versuchen die API-Kunden zu lösen? Welche Daten benötigen sie?", "resource.graphql-canvas.tips": "Introspektion zur Validierung von Typdefinitionen verwenden", - "resource.interaction-canvas.title": "Interaction Canvas", + "resource.interaction-canvas.title": "Interaktions-Canvas", "resource.interaction-canvas.description": "Definieren Sie API-Interaktionen, Arbeitsabläufe und erwartete Antworten, um ein einheitliches API-Erlebnis zu gewährleisten.", "resource.interaction-canvas.outcomes": "Klare API-Interaktionsabläufe", "resource.interaction-canvas.steps": "Zuordnung von API-Interaktionen zu Benutzeraufgaben", "resource.interaction-canvas.tips": "Beginnen Sie mit allgemeinen Anwendungsfällen, bevor Sie sich mit Sonderfällen befassen", - "resource.location-canvas.title": "Location Canvas", + "resource.location-canvas.title": "Standort-Canvas", "resource.location-canvas.description": "Kartieren Sie die Standorte von API-Anbietern und -Verbrauchern, um die Einhaltung von Vorschriften und die Leistung in verschiedenen Regionen sicherzustellen.", "resource.location-canvas.outcomes": "Einhaltung der örtlichen Vorschriften", "resource.location-canvas.steps": "Karte der Standorte von API-Anbietern.", "resource.location-canvas.tips": "Zusammenarbeit mit Rechts- und Compliance-Teams", - "resource.rest-canvas.title": "REST Canvas", + "resource.rest-canvas.title": "REST-Canvas", "resource.rest-canvas.description": "Entwurf von APIs unter Verwendung von RESTful-Prinzipien, Definition von Ressourcen, Verben und Beispielanforderungen und -antworten.", "resource.rest-canvas.outcomes": "Einheitliches RESTful API-Design", "resource.rest-canvas.steps": "Identifizierung der wichtigsten Ressourcen, die von der API bereitgestellt werden", @@ -255,8 +255,8 @@ "resource.competitor-analysis-template.tips.1": "Gemeinsame Nutzung durch Geschäfts- und Technikfunktionen", "resource.contract-first-design.outcomes.1": "Standardisierter Ansatz mit Contract First Design", "resource.contract-first-design.outcomes.2": "Verbesserte Umsetzung der entsprechenden API-Praktiken", - "resource.contract-first-design.steps.1": "Define interface contracts, schemas, responsibilities, usage rules, examples, and lifecycle expectations.", - "resource.contract-first-design.steps.2": "Use machine-readable formats such as OpenAPI, AsyncAPI, event schemas, message schemas, file schemas, data contracts, or interface specifications where possible.", + "resource.contract-first-design.steps.1": "Definieren Sie Schnittstellenverträge, Schemas, Verantwortlichkeiten, Nutzungsregeln, Beispiele und Lebenszykluserwartungen.", + "resource.contract-first-design.steps.2": "Verwenden Sie nach Möglichkeit maschinenlesbare Formate wie OpenAPI, AsyncAPI, Event-Schemas, Nachrichten-Schemas, Datei-Schemas, Datenverträge oder Schnittstellenspezifikationen.", "resource.contract-first-design.tips.1": "Gemeinsame Nutzung durch Geschäfts- und Technikfunktionen", "resource.cross-functional-collaboration-best-practices.outcomes.1": "Standardisierter Ansatz mit funktionsübergreifenden Best Practices für die Zusammenarbeit", "resource.cross-functional-collaboration-best-practices.outcomes.2": "Verbesserte Umsetzung der entsprechenden API-Praktiken", @@ -346,22 +346,22 @@ "resource.business-impact-canvas.tips.2": "Dokumentieren Sie neben den erwarteten Vorteilen auch die Auswirkungen des Nicht-Umsetzens.", "resource.capacity-canvas.outcomes.1": "Vorbereitet auf zukünftige Konsumtrends", "resource.capacity-canvas.outcomes.2": "Definierte Caching- und Ratenbegrenzungsstrategien", - "resource.capacity-canvas.steps.1": "Future Consumption Trends: Estimate future demand and growth assumptions.", - "resource.capacity-canvas.steps.2": "Peak Load and Availability Requirements: Quantify peak load and availability needs.", - "resource.capacity-canvas.steps.3": "Caching, rate limiting, and scaling approaches: Record architecture follow-up options where capacity requires them.", + "resource.capacity-canvas.steps.1": "Zukünftige Nutzungstrends: Schätzen Sie künftige Nachfrage und Wachstumsannahmen.", + "resource.capacity-canvas.steps.2": "Spitzenlast- und Verfügbarkeitsanforderungen: Quantifizieren Sie Spitzenlast und Verfügbarkeitsbedarf.", + "resource.capacity-canvas.steps.3": "Caching, Rate Limiting und Skalierungsansätze: Halten Sie Architektur-Folgeoptionen fest, wenn die Kapazität sie erfordert.", "resource.capacity-canvas.steps.4": "Skalierungsstrategien vorschlagen", "resource.capacity-canvas.tips.1": "Szenarien für Nutzungsspitzen definieren", "resource.capacity-canvas.tips.2": "Skalierbarkeitstests in die Planungsphase einbeziehen", - "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.customer-journey-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.customer-journey-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.customer-journey-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.customer-journey-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", "resource.customer-journey-canvas.steps.3": "Abbildung von Fahrtschritten mit Ein- und Ausgängen", "resource.customer-journey-canvas.steps.4": "Kundenbedürfnisse identifizieren", "resource.customer-journey-canvas.steps.5": "Kundengewinne zusammenfassen", "resource.customer-journey-canvas.steps.6": "Definition der erforderlichen Inputs und der daraus resultierenden Outputs", "resource.customer-journey-canvas.steps.7": "Definieren Sie API-Interaktionen für jeden Schritt", - "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.customer-journey-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", "resource.event-canvas.outcomes.1": "Ereignisauslöser und Verarbeitungslogik löschen", "resource.event-canvas.outcomes.2": "Verbesserte Reaktionsfähigkeit auf Änderungen in Echtzeit", "resource.event-canvas.steps.1": "Definieren Sie Auslöser für jedes Ereignis", @@ -404,7 +404,7 @@ "resource.rest-canvas.steps.3": "Geben Sie Beispiele für Anfragen und Antworten für jedes Verb an.", "resource.rest-canvas.tips.1": "Sicherstellen, dass Ressourcen-URIs intuitiv und konsistent sind", "resource.rest-canvas.tips.2": "Fehlerbehandlung und Antwortcodes dokumentieren", - "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas", + "resource.capability-value-proposition-canvas.title": "Fähigkeits-Wertversprechen-Canvas", "resource.capability-value-proposition-canvas.description": "Ein technologieunabhängiges Canvas zur Zuordnung von Nutzeraufgaben, Gewinnen, Problemen und möglichen wiederverwendbaren Capabilities, bevor ein Implementierungsstil ausgewählt wird.", "resource.capability-value-proposition-canvas.outcomes": "Klare Wertpositionierung der wiederverwendbaren Capability", "resource.capability-value-proposition-canvas.outcomes.1": "Nutzeraufgaben, Gewinne und Probleme ohne technologische Vorannahme erfasst", @@ -415,7 +415,7 @@ "resource.capability-value-proposition-canvas.steps.3": "Gruppieren Sie die Merkmale zu möglichen wiederverwendbaren Capabilities.", "resource.capability-value-proposition-canvas.tips": "Bleiben Sie technologieunabhängig, bis die Anforderungen auf einen Stil hinweisen.", "resource.capability-value-proposition-canvas.tips.1": "Verwenden Sie dies anstelle des API Value Proposition Canvas, wenn API noch nicht der gewählte Implementierungsstil ist.", - "resource.capability-business-model-canvas.title": "Capability Business Model Canvas", + "resource.capability-business-model-canvas.title": "Fähigkeits-Geschäftsmodell-Canvas", "resource.capability-business-model-canvas.description": "Ein Business Model Canvas für wiederverwendbare Integrations-Capabilities, das Wert, Nutzer, Verantwortung, Einbindung, Kosten und Nutzen abdeckt, ohne API-Bereitstellung vorauszusetzen.", "resource.capability-business-model-canvas.outcomes": "Tragfähiges Betriebsmodell für die wiederverwendbare Capability", "resource.capability-business-model-canvas.outcomes.1": "Verantwortung, Nutzer, Kanäle, Partner und Supportbedarf geklärt", @@ -428,7 +428,7 @@ "resource.capability-business-model-canvas.steps.5": "Validieren Sie das Modell mit Nutzern, Produzenten und Governance-Stakeholdern.", "resource.capability-business-model-canvas.tips": "Verwenden Sie dies anstelle des API Business Model Canvas, wenn der Implementierungsstil noch offen ist.", "resource.capability-business-model-canvas.tips.1": "Fokussieren Sie auf die Tragfähigkeit der wiederverwendbaren Capability, nicht auf eine einmalige Verbindung.", - "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas", + "resource.consumer-experience-requirements-canvas.title": "Canvas für Anforderungen an das Nutzererlebnis", "resource.consumer-experience-requirements-canvas.description": "Ein Anforderungen-Canvas für nutzerbezogene Experience- und nichtfunktionale Anforderungen, die die spätere Architekturentscheidung steuern sollen.", "resource.consumer-experience-requirements-canvas.outcomes": "Technologieunabhängige Nutzeranforderungen", "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience- und nichtfunktionale Anforderungen vor Designbeginn erfasst", @@ -519,9 +519,9 @@ "resource.automation-readiness-checklist.outcomes": "Readiness-Entscheidung für die Automatisierung", "resource.automation-readiness-checklist.outcomes.1": "Freigabeentscheidung als bereit, unter Bedingungen bereit, Nachbesserung erforderlich oder nicht genehmigt festgehalten", "resource.automation-readiness-checklist.outcomes.2": "Nachweise, blockierende Befunde, Restrisiken, Bedingungen, Nachbesserungsmaßnahmen, Entscheidungsverantwortung und Entscheidungsdatum vor der Freigabe dokumentiert", - "resource.automation-readiness-checklist.steps": "Review completed operating model, workflow design, business rules, controls, access, data handling, exception paths, and evidence.", + "resource.automation-readiness-checklist.steps": "Prüfen Sie das fertiggestellte Betriebsmodell, Workflow-Design, Geschäftsregeln, Kontrollen, Zugriff, Datenverarbeitung, Ausnahmefälle und Nachweise.", "resource.automation-readiness-checklist.steps.1": "Identifizieren Sie blockierende Befunde, akzeptierte Restrisiken, fehlende Nachweise und erforderliche Nachbesserungsmaßnahmen.", - "resource.automation-readiness-checklist.steps.2": "Record the release decision, decision owner, decision date, conditions, and follow-up actions.", + "resource.automation-readiness-checklist.steps.2": "Halten Sie Release-Entscheidung, Entscheidungsverantwortlichen, Entscheidungsdatum, Bedingungen und Folgeaktionen fest.", "resource.automation-readiness-checklist.steps.3": "Dokumentieren Sie ungelöste Lücken, Entscheidungen und akzeptierte Risiken vor der Veröffentlichung.", "resource.automation-readiness-checklist.tips": "Verwenden Sie die Checkliste vor der Veröffentlichung und erneut nach wesentlichen Workflow- oder Regeländerungen.", "resource.automation-readiness-checklist.tips.1": "Machen Sie menschliche Aufsicht und Ausnahmebehandlung in den Nachweisen explizit.", @@ -542,107 +542,107 @@ "resource.api-testing-best-practices.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.", "resource.apiops-CI-CD-for-apis.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.", "resource.api-audit-checklist.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.", - "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", - "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", - "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", - "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", - "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", - "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", - "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", - "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", - "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", - "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", - "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", - "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", - "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", - "resource.user-operator-experience-requirements.outcomes.1": "Availability, timeliness, permissions, support, recovery, observability, and activation needs captured", - "resource.user-operator-experience-requirements.outcomes.2": "Constraints ready for later architecture, workflow, and capacity decisions", - "resource.user-operator-experience-requirements.steps": "Capture user, operator, approver, and support goals for the target process.", - "resource.user-operator-experience-requirements.steps.1": "Clarify availability, timeliness, volume, data quality, permissions, activation, changes, support, observability, recovery, and continuity expectations.", - "resource.user-operator-experience-requirements.steps.2": "Translate the expectations into constraints for later automation design without choosing the implementation mechanism.", - "resource.user-operator-experience-requirements.tips": "Use this label in the Automation Cycle instead of API consumer wording.", - "resource.user-operator-experience-requirements.tips.1": "Keep the shared underlying requirements canvas intact for other cycles.", - "resource.automation-monitoring-value-metrics.title": "Automation Monitoring and Value Metrics", + "resource.automation-opportunity-canvas.title": "Canvas für Automatisierungshypothese und Validierung", + "resource.automation-opportunity-canvas.description": "Überführen Sie vorhandene Nachweise zu Journey, Wert, Auswirkungen, Domäne und Kapazität in eine testbare Automatisierungsentscheidung.", + "resource.automation-opportunity-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.automation-opportunity-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.automation-opportunity-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.automation-opportunity-canvas.steps": "Verwenden Sie frühere Canvas-Ergebnisse wieder. Halten Sie nur die verbleibende Hypothese, Unsicherheiten, Validierung und Entscheidung fest.", + "resource.automation-opportunity-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.automation-opportunity-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.automation-opportunity-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.automation-opportunity-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.automation-workflow-canvas.title": "Automatisierungs-Workflow-Canvas", + "resource.automation-workflow-canvas.description": "Entwerfen Sie den internen Workflow, der zur Erreichung der ausgewählten Kunden- und Fähigkeitsergebnisse benötigt wird.", + "resource.automation-workflow-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.automation-workflow-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.automation-workflow-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.automation-workflow-canvas.steps": "Verwenden Sie Nachweise aus Customer Journey, Wertversprechen, Domäne und Validierung wieder. Definieren Sie die interne Arbeit, verteilen Sie sie zwischen Menschen und Automatisierung und ergänzen Sie nur Ausführungsdetails.", + "resource.automation-workflow-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.automation-workflow-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.automation-workflow-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.automation-workflow-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.automation-architecture-decision-canvas.title": "Canvas für Automatisierungsarchitektur-Entscheidung", + "resource.automation-architecture-decision-canvas.description": "Wählen Sie den Umsetzungsansatz anhand bereits gesammelter Nachweise.", + "resource.automation-architecture-decision-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.automation-architecture-decision-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.automation-architecture-decision-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.automation-architecture-decision-canvas.steps": "Führen Sie Beschränkungen und Verantwortlichkeitsentscheidungen weiter. Vergleichen Sie nur tragfähige Mechanismen und halten Sie anschließend Entscheidung und verbleibende Risiken fest.", + "resource.automation-architecture-decision-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.automation-architecture-decision-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.automation-architecture-decision-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.automation-architecture-decision-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.automation-readiness-operations-canvas.title": "Canvas für Automatisierungsbereitschaft und Betrieb", + "resource.automation-readiness-operations-canvas.description": "Bereiten Sie die minimal erforderlichen Betriebsnachweise vor der Bereitschaftsprüfung vor.", + "resource.automation-readiness-operations-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.automation-readiness-operations-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.automation-readiness-operations-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.automation-readiness-operations-canvas.steps": "Verwenden Sie Designentscheidungen wieder. Halten Sie Verantwortlichkeit, betriebliche Regelungen, Nachweise, Wiederherstellung und verbleibende Bereitschaftslücken fest.", + "resource.automation-readiness-operations-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.automation-readiness-operations-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.automation-readiness-operations-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.automation-readiness-operations-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.user-operator-experience-requirements.title": "Anforderungen an Nutzer- und Operator-Erlebnis", + "resource.user-operator-experience-requirements.description": "Eine zyklusspezifische Sicht auf Erlebnis-, Betriebs- und nichtfunktionale Anforderungen für Automatisierungsnutzer, Operatoren, Genehmigende und Support-Teams.", + "resource.user-operator-experience-requirements.outcomes": "Erwartungen von Nutzern und Operatoren sind geklärt", + "resource.user-operator-experience-requirements.outcomes.1": "Anforderungen an Verfügbarkeit, Rechtzeitigkeit, Berechtigungen, Support, Wiederherstellung, Beobachtbarkeit und Aktivierung sind erfasst", + "resource.user-operator-experience-requirements.outcomes.2": "Beschränkungen sind für spätere Architektur-, Workflow- und Kapazitätsentscheidungen vorbereitet", + "resource.user-operator-experience-requirements.steps": "Erfassen Sie Ziele von Nutzern, Operatoren, Genehmigenden und Support für den Zielprozess.", + "resource.user-operator-experience-requirements.steps.1": "Klären Sie Erwartungen an Verfügbarkeit, Rechtzeitigkeit, Volumen, Datenqualität, Berechtigungen, Aktivierung, Änderungen, Support, Beobachtbarkeit, Wiederherstellung und Kontinuität.", + "resource.user-operator-experience-requirements.steps.2": "Übersetzen Sie die Erwartungen in Beschränkungen für das spätere Automatisierungsdesign, ohne den Umsetzungsmechanismus auszuwählen.", + "resource.user-operator-experience-requirements.tips": "Verwenden Sie diese Bezeichnung im Automatisierungszyklus statt API-Consumer-Formulierungen.", + "resource.user-operator-experience-requirements.tips.1": "Lassen Sie den gemeinsam genutzten zugrunde liegenden Anforderungs-Canvas für andere Zyklen unverändert.", + "resource.automation-monitoring-value-metrics.title": "Automatisierungsmonitoring und Wertmetriken", "resource.automation-monitoring-value-metrics.description": "Anleitung zur Messung von Ergebnissen, operativer Leistung, Nutzerverhalten, Risiko, Wiederherstellung, realisiertem Wert, Hypothesenlernen und Lifecycle-Entscheidungen nach dem Rollout.", - "resource.automation-monitoring-value-metrics.outcomes": "Automation monitoring, value, and learning evidence", - "resource.automation-monitoring-value-metrics.outcomes.1": "Actual outcomes, run success, failure, exception, retry, intervention, processing time, waiting time, correction, incident, adoption, and benefit signals reviewed", - "resource.automation-monitoring-value-metrics.outcomes.2": "Automation Hypothesis assumptions reviewed and improvement, expansion, redesign, or retirement decisions prioritized", - "resource.automation-monitoring-value-metrics.steps": "Outcomes and value: compare expected process, user, and business outcomes with actual evidence.", - "resource.automation-monitoring-value-metrics.steps.1": "Operational performance: review successful runs, failures, partial completions, exceptions, retries, timeouts, interventions, processing time, waiting time, and cost.", - "resource.automation-monitoring-value-metrics.steps.2": "User, risk, and recovery signals: review errors, corrections, unsafe actions, bypassing, mistrust, support needs, fallback events, and recovery failures.", - "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", + "resource.automation-monitoring-value-metrics.outcomes": "Nachweise zu Automatisierungsmonitoring, Wert und Lernen", + "resource.automation-monitoring-value-metrics.outcomes.1": "Tatsächliche Ergebnisse, erfolgreiche Läufe, Fehler, Ausnahmen, Wiederholungen, Eingriffe, Verarbeitungszeit, Wartezeit, Korrekturen, Vorfälle, Einführung und Nutzensignale wurden geprüft", + "resource.automation-monitoring-value-metrics.outcomes.2": "Annahmen der Automatisierungshypothese wurden geprüft und Entscheidungen zu Verbesserung, Erweiterung, Neugestaltung oder Stilllegung priorisiert", + "resource.automation-monitoring-value-metrics.steps": "Ergebnisse und Wert: Vergleichen Sie erwartete Prozess-, Nutzer- und Geschäftsergebnisse mit tatsächlichen Nachweisen.", + "resource.automation-monitoring-value-metrics.steps.1": "Operative Leistung: Prüfen Sie erfolgreiche Läufe, Fehler, Teilabschlüsse, Ausnahmen, Wiederholungen, Timeouts, Eingriffe, Verarbeitungszeit, Wartezeit und Kosten.", + "resource.automation-monitoring-value-metrics.steps.2": "Nutzer-, Risiko- und Wiederherstellungssignale: Prüfen Sie Fehler, Korrekturen, unsichere Aktionen, Umgehungen, Misstrauen, Supportbedarf, Fallback-Ereignisse und Wiederherstellungsfehler.", + "resource.automation-monitoring-value-metrics.steps.3": "Lernen und Lebenszyklusentscheidung: Entscheiden Sie, welche Hypothesenannahmen bestätigt oder verworfen wurden und ob verbessert, erweitert, eingeschränkt, neu gestaltet, pausiert, stillgelegt oder Backlog-Einträge ergänzt werden sollen.", "resource.automation-monitoring-value-metrics.tips": "Monitoring verwandelt operative, Nutzer-, Risiko- und Wertnachweise in Lifecycle-Entscheidungen und einen Verbesserungs-Backlog.", - "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", - "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", - "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", - "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", - "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", - "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", - "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", - "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", - "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", - "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.automation-monitoring-value-metrics.tips.1": "Beziehen Sie Signale ein, die Einführung, Vertrauen, Bedarf an menschlicher Aufsicht, Wiederherstellungsbedarf und realisierten Wert zeigen.", + "resource.integration-capability-hypothesis-canvas.title": "Canvas zur Validierung der Integrationsfähigkeit", + "resource.integration-capability-hypothesis-canvas.description": "Validieren Sie, ob eine vorgeschlagene wiederverwendbare Integrationsfähigkeit weiterverfolgt werden soll.", + "resource.integration-capability-hypothesis-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.integration-capability-hypothesis-canvas.steps": "Verwenden Sie Nachweise zu Journey, Wert, Domäne, Geschäftsmodell, Auswirkungen und Kapazität wieder, statt sie erneut darzustellen.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.integration-capability-hypothesis-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.integration-consumer-provider-requirements-canvas.title": "Canvas für Verpflichtungen von Integrationsnutzern und -anbietern", + "resource.integration-consumer-provider-requirements-canvas.description": "Vereinbaren Sie die Verantwortlichkeiten, die für Nutzung und Bereitstellung einer wiederverwendbaren Integrationsfähigkeit erforderlich sind.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.integration-consumer-provider-requirements-canvas.steps": "Führen Sie Nutzer, Anwendungsfälle, Servicebedarfe und Beschränkungen weiter. Halten Sie Verpflichtungen fest, statt Anforderungen erneut zu ermitteln.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.integration-architecture-decision-canvas.title": "Canvas für Integrationsarchitektur-Entscheidung", + "resource.integration-architecture-decision-canvas.description": "Wählen Sie Integrationsstil und Plattform anhand bereits gesammelter Nachweise.", + "resource.integration-architecture-decision-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.integration-architecture-decision-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.integration-architecture-decision-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.integration-architecture-decision-canvas.steps": "Führen Sie Nutzerverpflichtungen, Auswirkungen, Standort und Kapazität weiter. Vergleichen Sie nur tragfähige Stile und halten Sie die Entscheidung fest.", + "resource.integration-architecture-decision-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.integration-architecture-decision-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.integration-architecture-decision-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.integration-architecture-decision-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.integration-readiness-operations-canvas.title": "Canvas für Integrationsbereitschaft und Betrieb", + "resource.integration-readiness-operations-canvas.description": "Bereiten Sie die minimal erforderlichen Betriebsnachweise vor der Prüfung der Integrationsbereitschaft vor.", + "resource.integration-readiness-operations-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.integration-readiness-operations-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.integration-readiness-operations-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.integration-readiness-operations-canvas.steps": "Verwenden Sie Verträge und Designentscheidungen wieder. Halten Sie Verantwortlichkeit, Betrieb, Nachweise, Wiederherstellung und verbleibende Bereitschaftslücken fest.", + "resource.integration-readiness-operations-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.integration-readiness-operations-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.integration-readiness-operations-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.integration-readiness-operations-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", "resource.integration-consumer-onboarding-guide.title": "Leitfaden für Integrations-Consumer-Onboarding", "resource.integration-consumer-onboarding-guide.description": "Leitfaden für Integrations-Consumer-Onboarding unterstützt die Planung, Entscheidung, Lieferung, Veröffentlichung oder Verbesserung einer wiederverwendbaren Integrationsfähigkeit.", "resource.integration-consumer-onboarding-guide.outcomes": "Dokumentierte Integrationsgrundlage", @@ -813,66 +813,66 @@ "resource.integration-lifecycle-management-guide.steps.2": "Nutzen Sie die Ergebnisse für Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", "resource.integration-lifecycle-management-guide.tips": "Passen Sie diese Ressource an den gewählten Integrationsstil an.", "resource.integration-lifecycle-management-guide.tips.1": "Beziehen Sie Producer, Consumer, Plattform, Betrieb, Security, Compliance und Business ein.", - "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", - "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", - "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", - "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", - "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", - "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", - "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", - "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", - "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", - "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", - "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", - "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", - "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", - "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", - "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", - "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", - "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-solution-design-canvas.title": "Canvas für Integrationslösungsdesign", + "resource.integration-solution-design-canvas.description": "Verfeinern Sie die ausgewählte Architektur zu einem umsetzbaren Integrationsdesign.", + "resource.integration-solution-design-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.integration-solution-design-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.integration-solution-design-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.integration-solution-design-canvas.steps": "Verwenden Sie den ausgewählten Stil, Domänenkonzepte, Interaktionsbedarfe und Verpflichtungen wieder. Ergänzen Sie nur umsetzungsspezifisches Design.", + "resource.integration-solution-design-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.integration-solution-design-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.integration-solution-design-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.integration-solution-design-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.capability-hypothesis-canvas.title": "Canvas zur Fähigkeitsvalidierung", + "resource.capability-hypothesis-canvas.description": "Validieren Sie, ob eine vorgeschlagene wiederverwendbare digitale Fähigkeit weiterverfolgt werden soll.", + "resource.capability-hypothesis-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.capability-hypothesis-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.capability-hypothesis-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.capability-hypothesis-canvas.steps": "Verwenden Sie Ergebnisse zu Journey, Wertversprechen, Geschäftsmodell, Auswirkungen, Domäne und Kapazität wieder, statt sie zu wiederholen.", + "resource.capability-hypothesis-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.capability-hypothesis-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.capability-hypothesis-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.capability-hypothesis-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.capability-consumer-producer-requirements-canvas.title": "Canvas für Verpflichtungen von Fähigkeitsnutzern und -produzenten", + "resource.capability-consumer-producer-requirements-canvas.description": "Vereinbaren Sie gegenseitige Verpflichtungen für Bereitstellung und Nutzung einer wiederverwendbaren Fähigkeit.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.capability-consumer-producer-requirements-canvas.steps": "Verwenden Sie Nutzer, Wert, Kanäle, Servicebedarfe und Verantwortlichkeit aus früheren Canvases wieder. Erfassen Sie nur vereinbarte Verpflichtungen und Lücken.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.capability-architecture-decision-canvas.title": "Canvas für Fähigkeitsarchitektur-Entscheidung", + "resource.capability-architecture-decision-canvas.description": "Wählen Sie anhand bereits gesammelter Nachweise, wie die Fähigkeit bereitgestellt wird.", + "resource.capability-architecture-decision-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.capability-architecture-decision-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.capability-architecture-decision-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.capability-architecture-decision-canvas.steps": "Führen Sie Wert, Verpflichtungen, Auswirkungen, Standort, Kapazität und Domänenentscheidungen weiter. Vergleichen Sie nur tragfähige Umsetzungsstile.", + "resource.capability-architecture-decision-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.capability-architecture-decision-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.capability-architecture-decision-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.capability-architecture-decision-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.capability-solution-design-canvas.title": "Canvas für Fähigkeitslösungsdesign", + "resource.capability-solution-design-canvas.description": "Verfeinern Sie den ausgewählten Umsetzungsstil zu einem klaren, nutzerorientierten Fähigkeitsdesign.", + "resource.capability-solution-design-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.capability-solution-design-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.capability-solution-design-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.capability-solution-design-canvas.steps": "Verwenden Sie Ergebnisse zu Wert, Domäne, Interaktion, Verpflichtungen und Architektur wieder. Ergänzen Sie nur lösungsspezifisches Design.", + "resource.capability-solution-design-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.capability-solution-design-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.capability-solution-design-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.capability-solution-design-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", + "resource.capability-readiness-operations-canvas.title": "Canvas für Fähigkeitsbereitschaft und Betrieb", + "resource.capability-readiness-operations-canvas.description": "Bereiten Sie die minimal erforderlichen Betriebsnachweise vor der Prüfung der Fähigkeitsbereitschaft vor.", + "resource.capability-readiness-operations-canvas.outcomes": "Ein fokussiertes Entscheidungs- oder Designartefakt, das frühere Nachweise wiederverwendet", + "resource.capability-readiness-operations-canvas.outcomes.1": "Frühere Canvas-Ergebnisse werden referenziert statt wiederholt", + "resource.capability-readiness-operations-canvas.outcomes.2": "Die nächste Entscheidung, der nächste Designschritt oder die Bereitschaftslücke ist explizit", + "resource.capability-readiness-operations-canvas.steps": "Verwenden Sie Geschäftsmodell, Verpflichtungen und Lösungsdesign wieder. Halten Sie nur operative Verantwortlichkeit, Nachweise, Kontinuität und Bereitschaftslücken fest.", + "resource.capability-readiness-operations-canvas.steps.1": "Füllen Sie nur die Abschnitte aus, die eine neue Entscheidung oder Verfeinerung hinzufügen.", + "resource.capability-readiness-operations-canvas.steps.2": "Übernehmen Sie die daraus entstehenden Entscheidungen in die nächste Station.", + "resource.capability-readiness-operations-canvas.tips": "Verlinken Sie auf frühere Canvases, statt deren Inhalte zu kopieren.", + "resource.capability-readiness-operations-canvas.tips.1": "Nutzen Sie unterstützende Canvases nur, wenn die erforderlichen Nachweise noch nicht vorhanden sind.", "resource.capability-consumer-onboarding-guide.title": "Leitfaden für Capability Consumer Onboarding", "resource.capability-consumer-onboarding-guide.description": "Leitfaden für Capability Consumer Onboarding unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", "resource.capability-consumer-onboarding-guide.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", @@ -903,7 +903,7 @@ "resource.capability-ownership-producer-responsibilities-guide.steps.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", "resource.capability-ownership-producer-responsibilities-guide.tips": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", "resource.capability-ownership-producer-responsibilities-guide.tips.1": "Behandeln Sie unterstützende Canvases als optionale Nachweise, nicht als Pflichtarbeit.", - "resource.capability-delivery-guide.title": "Capability Delivery Guide", + "resource.capability-delivery-guide.title": "Leitfaden zur Fähigkeitsbereitstellung", "resource.capability-delivery-guide.description": "Capability Delivery Guide unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", "resource.capability-delivery-guide.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", "resource.capability-delivery-guide.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", @@ -963,7 +963,7 @@ "resource.capability-support-lifecycle-guide.steps.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", "resource.capability-support-lifecycle-guide.tips": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", "resource.capability-support-lifecycle-guide.tips.1": "Behandeln Sie unterstützende Canvases als optionale Nachweise, nicht als Pflichtarbeit.", - "resource.capability-readiness-checklist.title": "Capability Readiness Checklist", + "resource.capability-readiness-checklist.title": "Checkliste zur Fähigkeitsbereitschaft", "resource.capability-readiness-checklist.description": "Capability Readiness Checklist unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", "resource.capability-readiness-checklist.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", "resource.capability-readiness-checklist.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", @@ -1003,7 +1003,7 @@ "resource.capability-publishing-discovery-guide.steps.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", "resource.capability-publishing-discovery-guide.tips": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", "resource.capability-publishing-discovery-guide.tips.1": "Behandeln Sie unterstützende Canvases als optionale Nachweise, nicht als Pflichtarbeit.", - "resource.capability-service-agreement-template.title": "Capability Service Agreement Template", + "resource.capability-service-agreement-template.title": "Vorlage für Fähigkeits-Servicevereinbarung", "resource.capability-service-agreement-template.description": "Capability Service Agreement Template unterstützt den jeweiligen Capability-Schritt mit spezifischen Entscheidungen, Nachweisen, Verantwortlichkeiten, Risiken und nächsten Schritten.", "resource.capability-service-agreement-template.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", "resource.capability-service-agreement-template.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", diff --git a/src/data/method/de/labels.stakeholders.json b/src/data/method/de/labels.stakeholders.json index 2c42cf8..a5fba9b 100644 --- a/src/data/method/de/labels.stakeholders.json +++ b/src/data/method/de/labels.stakeholders.json @@ -2,13 +2,13 @@ "stakeholder.involvement.lead": "Federführend", "stakeholder.involvement.core": "Kern", "stakeholder.involvement.consulted": "Konsultiert", - "stakeholder.business-owner.title": "Business Owner", + "stakeholder.business-owner.title": "Fachlicher Verantwortlicher", "stakeholder.business-owner.description": "Vertritt Geschäftsziele, Finanzierung und erwartete Ergebnisse der Capability-, API- oder Automatisierungsinitiative.", "stakeholder.api-program-owner.title": "API-Programmverantwortlicher", "stakeholder.api-program-owner.description": "Koordiniert API-Portfolio-Praktiken, organisatorische Ausrichtung und langfristige Entwicklung von API-Capabilities.", - "stakeholder.api-product-owner.title": "API Product Owner", + "stakeholder.api-product-owner.title": "API-Produktverantwortlicher", "stakeholder.api-product-owner.description": "Steuert API-Chance, Priorisierung und produktbezogene Entscheidungen über den gesamten Lebenszyklus hinweg.", - "stakeholder.capability-owner.title": "Capability Owner", + "stakeholder.capability-owner.title": "Fähigkeitsverantwortlicher", "stakeholder.capability-owner.description": "Verantwortet Vision, Wert, Prioritäten, Lebenszyklus und Wiederverwendung der Capability über Nutzer hinweg.", "stakeholder.domain-specialist.title": "Domain-Experte", "stakeholder.domain-specialist.description": "Bringt tiefes Wissen über Geschäftsdomäne, Konzepte, Regeln und Einschränkungen ein, die die Capability oder Schnittstelle widerspiegeln muss.", diff --git a/src/data/method/de/labels.stations.json b/src/data/method/de/labels.stations.json index 85c2651..ebde635 100644 --- a/src/data/method/de/labels.stations.json +++ b/src/data/method/de/labels.stations.json @@ -38,19 +38,19 @@ "station.api-audit.title": "Qualitäts- & Bereitschaftssicherung", "station.api-audit.description": "Prüfen Sie die Freigabebereitschaft anhand von Nachweisen aus Design, Tests, Betrieb, Berechtigungen, Monitoring, Support, Fallback, Rollback, Risiko und Ownership vor der Produktionsnutzung.", "station.api-audit.why_it_matters": "Eine formale Bereitschaftsentscheidung verhindert, dass Automatisierungslösungen ohne klare Nachweise, akzeptierte Risiken, Remediation-Maßnahmen sowie fachliche und betriebliche Ownership freigegeben werden.", - "station.api-audit.apply_in_work": "", + "station.api-audit.apply_in_work": "Nutzen Sie Bereitschaftsnachweise, um vor der Produktionsnutzung eine ausdrückliche Go-, bedingte Go- oder No-go-Entscheidung zu treffen.", "station.api-audit.outcomes": "Formale Bereitschaftsentscheidung", "station.api-audit.how_it_works": "Prüfen Sie abgeschlossenes Design, Testnachweise, Betriebsmodell, Berechtigungen, Credentials, Monitoring, Support, Fallback und Rollback.", "station.api-publishing.title": "Veröffentlichung & Enablement", "station.api-publishing.description": "Befähigen Sie freigegebene Lösungen, damit Benutzer, Betreiber, betroffene Teams, konsumierende Systeme, Servicekonsumenten und Support-Teams sie sicher übernehmen können.", "station.api-publishing.why_it_matters": "Automatisierungslösungen schaffen erst nach dem Rollout Wert, wenn betroffene Personen und konsumierende Systeme verstehen, was sich ändert, wie Zugriff und Betrieb funktionieren, wo Unterstützung verfügbar ist und wann der Rollout pausiert, erweitert oder zurückgerollt werden muss.", - "station.api-publishing.apply_in_work": "", + "station.api-publishing.apply_in_work": "Planen Sie Rollout, Befähigung, Support, Feedback und Rollback, damit freigegebene Lösungen sicher eingeführt werden können.", "station.api-publishing.outcomes": "Sicherer Rollout- und Enablement-Plan", "station.api-publishing.how_it_works": "Betroffene Personen und geänderte Arbeit: Wer wird die Freigabe nutzen, betreiben, unterstützen, genehmigen, konsumieren oder davon betroffen sein, und welche Verantwortlichkeiten, Entscheidungen, Übergaben oder Arbeitsweisen ändern sich?", "station.monitoring-and-improving.title": "Monitoring & Verbesserung", "station.monitoring-and-improving.description": "Überwachen Sie tatsächliche Ergebnisse, Betriebsleistung, Nutzerverhalten, Risiko, Wiederherstellung, realisierten Wert und Verbesserungsmöglichkeiten nach der Freigabe.", "station.monitoring-and-improving.why_it_matters": "Freigegebene Lösungen benötigen Nachweise, ob erwartete Ergebnisse erreicht werden, wo manuelle Intervention oder Wiederherstellung noch nötig ist und welche Lifecycle-Entscheidung als Nächstes getroffen werden sollte.", - "station.monitoring-and-improving.apply_in_work": "", + "station.monitoring-and-improving.apply_in_work": "Nutzen Sie operative, Nutzer-, Risiko- und Wertnachweise, um zu entscheiden, was verbessert, erweitert, eingeschränkt, pausiert oder stillgelegt werden soll.", "station.monitoring-and-improving.outcomes": "Gemessene Ergebnis-, Leistungs-, Risiko-, Wiederherstellungs- und Wertnachweise", "station.monitoring-and-improving.how_it_works": "Ergebnisse und Wert: Werden die erwarteten Prozess-, Nutzer- und Geschäftsergebnisse erreicht?", "station.user-experience.title": "Benutzerfreundlichkeit - Entwerfen Sie APIs mit dem Benutzer im Hinterkopf", @@ -468,197 +468,5 @@ "station.api-audit.how_it_works.4": "Dokumentieren Sie Entscheidungsverantwortliche, Entscheidungsdatum und verwendete Nachweise.", "station.api-audit.how_it_works.5": "Bestätigen Sie, dass nichts ohne klare fachliche und betriebliche Ownership freigegeben wird.", "station.api-publishing.how_it_works.3": "Feedback und Kontrolle: Wie werden Adoption, Vertrauen, tatsächliche Nutzung, Probleme und unerwartetes Verhalten überwacht, und welche Bedingungen lösen Pause, Rollback oder Rückkehr zum manuellen Betrieb aus?", - "station.monitoring-and-improving.how_it_works.3": "Lernen und Lifecycle-Entscheidung: Welche Hypothesenannahmen wurden bestätigt oder verworfen, und sollte die Lösung verbessert, erweitert, eingeschränkt, neu gestaltet, pausiert oder stillgelegt werden?", - "station.integration-capability-strategy.title": "Integration Capability Strategy", - "station.integration-capability-strategy.description": "Integration Capability Strategy klärt die nächsten Entscheidungen, Nachweise, Verantwortlichkeiten und Risiken für eine wiederverwendbare Integrationsfähigkeit. Use supporting canvases only where the necessary evidence does not already exist.", - "station.integration-capability-strategy.why_it_matters": "Die Integrationsarbeit bleibt konsistent, wenn Consumer, Producer, Plattform, Betrieb, Security, Compliance und Business dieselben Nachweise und Entscheidungen verwenden.", - "station.integration-capability-strategy.apply_in_work": "Nutzen Sie die stationsspezifischen Integrationsressourcen als primäre Arbeitsgrundlage.", - "station.integration-capability-strategy.outcomes": "Dokumentierte Integrationsentscheidung oder Arbeitsgrundlage", - "station.integration-capability-strategy.outcomes.1": "Relevante Verantwortlichkeiten, Nachweise und Randbedingungen geklärt", - "station.integration-capability-strategy.outcomes.2": "Risiken, Annahmen und nächste Schritte sichtbar", - "station.integration-capability-strategy.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.integration-capability-strategy.how_it_works": "Klären Sie Ziel, Umfang, Consumer, Producer und Plattformkontext.", - "station.integration-capability-strategy.how_it_works.1": "Dokumentieren Sie relevante Nachweise, Entscheidungen, Risiken und Verantwortlichkeiten.", - "station.integration-capability-strategy.how_it_works.2": "Prüfen Sie Abhängigkeiten zu Architektur, Design, Betrieb, Veröffentlichung und Monitoring.", - "station.integration-capability-strategy.how_it_works.3": "Halten Sie offene Punkte und nächste Schritte fest.", - "station.integration-consumer-requirements-onboarding.title": "Integration Consumer Requirements & Onboarding", - "station.integration-consumer-requirements-onboarding.description": "Integration Consumer Requirements & Onboarding klärt die nächsten Entscheidungen, Nachweise, Verantwortlichkeiten und Risiken für eine wiederverwendbare Integrationsfähigkeit.", - "station.integration-consumer-requirements-onboarding.why_it_matters": "Die Integrationsarbeit bleibt konsistent, wenn Consumer, Producer, Plattform, Betrieb, Security, Compliance und Business dieselben Nachweise und Entscheidungen verwenden.", - "station.integration-consumer-requirements-onboarding.apply_in_work": "Nutzen Sie die stationsspezifischen Integrationsressourcen als primäre Arbeitsgrundlage.", - "station.integration-consumer-requirements-onboarding.outcomes": "Dokumentierte Integrationsentscheidung oder Arbeitsgrundlage", - "station.integration-consumer-requirements-onboarding.outcomes.1": "Relevante Verantwortlichkeiten, Nachweise und Randbedingungen geklärt", - "station.integration-consumer-requirements-onboarding.outcomes.2": "Risiken, Annahmen und nächste Schritte sichtbar", - "station.integration-consumer-requirements-onboarding.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.integration-consumer-requirements-onboarding.how_it_works": "Klären Sie Ziel, Umfang, Consumer, Producer und Plattformkontext.", - "station.integration-consumer-requirements-onboarding.how_it_works.1": "Dokumentieren Sie relevante Nachweise, Entscheidungen, Risiken und Verantwortlichkeiten.", - "station.integration-consumer-requirements-onboarding.how_it_works.2": "Prüfen Sie Abhängigkeiten zu Architektur, Design, Betrieb, Veröffentlichung und Monitoring.", - "station.integration-consumer-requirements-onboarding.how_it_works.3": "Halten Sie offene Punkte und nächste Schritte fest.", - "station.integration-architecture-platform-decisions.title": "Integration Architecture & Platform Decisions", - "station.integration-architecture-platform-decisions.description": "Integration Architecture & Platform Decisions klärt die nächsten Entscheidungen, Nachweise, Verantwortlichkeiten und Risiken für eine wiederverwendbare Integrationsfähigkeit.", - "station.integration-architecture-platform-decisions.why_it_matters": "Die Integrationsarbeit bleibt konsistent, wenn Consumer, Producer, Plattform, Betrieb, Security, Compliance und Business dieselben Nachweise und Entscheidungen verwenden.", - "station.integration-architecture-platform-decisions.apply_in_work": "Nutzen Sie die stationsspezifischen Integrationsressourcen als primäre Arbeitsgrundlage.", - "station.integration-architecture-platform-decisions.outcomes": "Dokumentierte Integrationsentscheidung oder Arbeitsgrundlage", - "station.integration-architecture-platform-decisions.outcomes.1": "Relevante Verantwortlichkeiten, Nachweise und Randbedingungen geklärt", - "station.integration-architecture-platform-decisions.outcomes.2": "Risiken, Annahmen und nächste Schritte sichtbar", - "station.integration-architecture-platform-decisions.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.integration-architecture-platform-decisions.how_it_works": "Klären Sie Ziel, Umfang, Consumer, Producer und Plattformkontext.", - "station.integration-architecture-platform-decisions.how_it_works.1": "Dokumentieren Sie relevante Nachweise, Entscheidungen, Risiken und Verantwortlichkeiten.", - "station.integration-architecture-platform-decisions.how_it_works.2": "Prüfen Sie Abhängigkeiten zu Architektur, Design, Betrieb, Veröffentlichung und Monitoring.", - "station.integration-architecture-platform-decisions.how_it_works.3": "Halten Sie offene Punkte und nächste Schritte fest.", - "station.integration-solution-design.title": "Integration Solution Design", - "station.integration-solution-design.description": "Integration Solution Design klärt die nächsten Entscheidungen, Nachweise, Verantwortlichkeiten und Risiken für eine wiederverwendbare Integrationsfähigkeit.", - "station.integration-solution-design.why_it_matters": "Die Integrationsarbeit bleibt konsistent, wenn Consumer, Producer, Plattform, Betrieb, Security, Compliance und Business dieselben Nachweise und Entscheidungen verwenden.", - "station.integration-solution-design.apply_in_work": "Nutzen Sie die stationsspezifischen Integrationsressourcen als primäre Arbeitsgrundlage.", - "station.integration-solution-design.outcomes": "Dokumentierte Integrationsentscheidung oder Arbeitsgrundlage", - "station.integration-solution-design.outcomes.1": "Relevante Verantwortlichkeiten, Nachweise und Randbedingungen geklärt", - "station.integration-solution-design.outcomes.2": "Risiken, Annahmen und nächste Schritte sichtbar", - "station.integration-solution-design.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.integration-solution-design.how_it_works": "Klären Sie Ziel, Umfang, Consumer, Producer und Plattformkontext.", - "station.integration-solution-design.how_it_works.1": "Dokumentieren Sie relevante Nachweise, Entscheidungen, Risiken und Verantwortlichkeiten.", - "station.integration-solution-design.how_it_works.2": "Prüfen Sie Abhängigkeiten zu Architektur, Design, Betrieb, Veröffentlichung und Monitoring.", - "station.integration-solution-design.how_it_works.3": "Halten Sie offene Punkte und nächste Schritte fest.", - "station.integration-delivery-operations.title": "Integration Delivery & Operations", - "station.integration-delivery-operations.description": "Integration Delivery & Operations klärt die nächsten Entscheidungen, Nachweise, Verantwortlichkeiten und Risiken für eine wiederverwendbare Integrationsfähigkeit.", - "station.integration-delivery-operations.why_it_matters": "Die Integrationsarbeit bleibt konsistent, wenn Consumer, Producer, Plattform, Betrieb, Security, Compliance und Business dieselben Nachweise und Entscheidungen verwenden.", - "station.integration-delivery-operations.apply_in_work": "Nutzen Sie die stationsspezifischen Integrationsressourcen als primäre Arbeitsgrundlage.", - "station.integration-delivery-operations.outcomes": "Dokumentierte Integrationsentscheidung oder Arbeitsgrundlage", - "station.integration-delivery-operations.outcomes.1": "Relevante Verantwortlichkeiten, Nachweise und Randbedingungen geklärt", - "station.integration-delivery-operations.outcomes.2": "Risiken, Annahmen und nächste Schritte sichtbar", - "station.integration-delivery-operations.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.integration-delivery-operations.how_it_works": "Klären Sie Ziel, Umfang, Consumer, Producer und Plattformkontext.", - "station.integration-delivery-operations.how_it_works.1": "Dokumentieren Sie relevante Nachweise, Entscheidungen, Risiken und Verantwortlichkeiten.", - "station.integration-delivery-operations.how_it_works.2": "Prüfen Sie Abhängigkeiten zu Architektur, Design, Betrieb, Veröffentlichung und Monitoring.", - "station.integration-delivery-operations.how_it_works.3": "Halten Sie offene Punkte und nächste Schritte fest.", - "station.integration-readiness-assurance.title": "Integration Readiness Assurance", - "station.integration-readiness-assurance.description": "Integration Readiness Assurance klärt die nächsten Entscheidungen, Nachweise, Verantwortlichkeiten und Risiken für eine wiederverwendbare Integrationsfähigkeit.", - "station.integration-readiness-assurance.why_it_matters": "Die Integrationsarbeit bleibt konsistent, wenn Consumer, Producer, Plattform, Betrieb, Security, Compliance und Business dieselben Nachweise und Entscheidungen verwenden.", - "station.integration-readiness-assurance.apply_in_work": "Nutzen Sie die stationsspezifischen Integrationsressourcen als primäre Arbeitsgrundlage.", - "station.integration-readiness-assurance.outcomes": "Dokumentierte Integrationsentscheidung oder Arbeitsgrundlage", - "station.integration-readiness-assurance.outcomes.1": "Relevante Verantwortlichkeiten, Nachweise und Randbedingungen geklärt", - "station.integration-readiness-assurance.outcomes.2": "Risiken, Annahmen und nächste Schritte sichtbar", - "station.integration-readiness-assurance.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.integration-readiness-assurance.how_it_works": "Klären Sie Ziel, Umfang, Consumer, Producer und Plattformkontext.", - "station.integration-readiness-assurance.how_it_works.1": "Dokumentieren Sie relevante Nachweise, Entscheidungen, Risiken und Verantwortlichkeiten.", - "station.integration-readiness-assurance.how_it_works.2": "Prüfen Sie Abhängigkeiten zu Architektur, Design, Betrieb, Veröffentlichung und Monitoring.", - "station.integration-readiness-assurance.how_it_works.3": "Halten Sie offene Punkte und nächste Schritte fest.", - "station.integration-publishing-enablement.title": "Integration Publishing & Enablement", - "station.integration-publishing-enablement.description": "Integration Publishing & Enablement klärt die nächsten Entscheidungen, Nachweise, Verantwortlichkeiten und Risiken für eine wiederverwendbare Integrationsfähigkeit.", - "station.integration-publishing-enablement.why_it_matters": "Die Integrationsarbeit bleibt konsistent, wenn Consumer, Producer, Plattform, Betrieb, Security, Compliance und Business dieselben Nachweise und Entscheidungen verwenden.", - "station.integration-publishing-enablement.apply_in_work": "Nutzen Sie die stationsspezifischen Integrationsressourcen als primäre Arbeitsgrundlage.", - "station.integration-publishing-enablement.outcomes": "Dokumentierte Integrationsentscheidung oder Arbeitsgrundlage", - "station.integration-publishing-enablement.outcomes.1": "Relevante Verantwortlichkeiten, Nachweise und Randbedingungen geklärt", - "station.integration-publishing-enablement.outcomes.2": "Risiken, Annahmen und nächste Schritte sichtbar", - "station.integration-publishing-enablement.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.integration-publishing-enablement.how_it_works": "Klären Sie Ziel, Umfang, Consumer, Producer und Plattformkontext.", - "station.integration-publishing-enablement.how_it_works.1": "Dokumentieren Sie relevante Nachweise, Entscheidungen, Risiken und Verantwortlichkeiten.", - "station.integration-publishing-enablement.how_it_works.2": "Prüfen Sie Abhängigkeiten zu Architektur, Design, Betrieb, Veröffentlichung und Monitoring.", - "station.integration-publishing-enablement.how_it_works.3": "Halten Sie offene Punkte und nächste Schritte fest.", - "station.integration-monitoring-improvement.title": "Integration Monitoring & Improvement", - "station.integration-monitoring-improvement.description": "Integration Monitoring & Improvement klärt die nächsten Entscheidungen, Nachweise, Verantwortlichkeiten und Risiken für eine wiederverwendbare Integrationsfähigkeit.", - "station.integration-monitoring-improvement.why_it_matters": "Die Integrationsarbeit bleibt konsistent, wenn Consumer, Producer, Plattform, Betrieb, Security, Compliance und Business dieselben Nachweise und Entscheidungen verwenden.", - "station.integration-monitoring-improvement.apply_in_work": "Nutzen Sie die stationsspezifischen Integrationsressourcen als primäre Arbeitsgrundlage.", - "station.integration-monitoring-improvement.outcomes": "Dokumentierte Integrationsentscheidung oder Arbeitsgrundlage", - "station.integration-monitoring-improvement.outcomes.1": "Relevante Verantwortlichkeiten, Nachweise und Randbedingungen geklärt", - "station.integration-monitoring-improvement.outcomes.2": "Risiken, Annahmen und nächste Schritte sichtbar", - "station.integration-monitoring-improvement.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.integration-monitoring-improvement.how_it_works": "Klären Sie Ziel, Umfang, Consumer, Producer und Plattformkontext.", - "station.integration-monitoring-improvement.how_it_works.1": "Dokumentieren Sie relevante Nachweise, Entscheidungen, Risiken und Verantwortlichkeiten.", - "station.integration-monitoring-improvement.how_it_works.2": "Prüfen Sie Abhängigkeiten zu Architektur, Design, Betrieb, Veröffentlichung und Monitoring.", - "station.integration-monitoring-improvement.how_it_works.3": "Halten Sie offene Punkte und nächste Schritte fest.", - "station.capability-strategy.title": "Capability Strategy", - "station.capability-strategy.description": "Capability Strategy klärt Fähigkeit, Consumer, Producer, Serviceerwartungen, Risiken, Nachweise und nächste Entscheidungen auf wiederverwendbarer Ebene.", - "station.capability-strategy.why_it_matters": "Die Capability Cycle bleibt über dem Implementierungsstil und verweist auf API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsdetails erst nach der Stilentscheidung.", - "station.capability-strategy.apply_in_work": "", - "station.capability-strategy.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "station.capability-strategy.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "station.capability-strategy.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "station.capability-strategy.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.capability-strategy.how_it_works": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "station.capability-strategy.how_it_works.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "station.capability-strategy.how_it_works.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "station.capability-strategy.how_it_works.3": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "station.capability-consumer-producer-requirements.title": "Consumer, Producer & Service Requirements", - "station.capability-consumer-producer-requirements.description": "Consumer, Producer & Service Requirements klärt Fähigkeit, Consumer, Producer, Serviceerwartungen, Risiken, Nachweise und nächste Entscheidungen auf wiederverwendbarer Ebene.", - "station.capability-consumer-producer-requirements.why_it_matters": "Die Capability Cycle bleibt über dem Implementierungsstil und verweist auf API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsdetails erst nach der Stilentscheidung.", - "station.capability-consumer-producer-requirements.apply_in_work": "", - "station.capability-consumer-producer-requirements.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "station.capability-consumer-producer-requirements.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "station.capability-consumer-producer-requirements.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "station.capability-consumer-producer-requirements.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.capability-consumer-producer-requirements.how_it_works": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "station.capability-consumer-producer-requirements.how_it_works.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "station.capability-consumer-producer-requirements.how_it_works.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "station.capability-consumer-producer-requirements.how_it_works.3": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "station.capability-architecture-platform-decisions.title": "Capability Architecture & Platform Decisions", - "station.capability-architecture-platform-decisions.description": "Capability Architecture & Platform Decisions klärt Fähigkeit, Consumer, Producer, Serviceerwartungen, Risiken, Nachweise und nächste Entscheidungen auf wiederverwendbarer Ebene.", - "station.capability-architecture-platform-decisions.why_it_matters": "Die Capability Cycle bleibt über dem Implementierungsstil und verweist auf API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsdetails erst nach der Stilentscheidung.", - "station.capability-architecture-platform-decisions.apply_in_work": "", - "station.capability-architecture-platform-decisions.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "station.capability-architecture-platform-decisions.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "station.capability-architecture-platform-decisions.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "station.capability-architecture-platform-decisions.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.capability-architecture-platform-decisions.how_it_works": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "station.capability-architecture-platform-decisions.how_it_works.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "station.capability-architecture-platform-decisions.how_it_works.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "station.capability-architecture-platform-decisions.how_it_works.3": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "station.capability-solution-interaction-design.title": "Capability Solution & Interaction Design", - "station.capability-solution-interaction-design.description": "Capability Solution & Interaction Design klärt Fähigkeit, Consumer, Producer, Serviceerwartungen, Risiken, Nachweise und nächste Entscheidungen auf wiederverwendbarer Ebene.", - "station.capability-solution-interaction-design.why_it_matters": "Die Capability Cycle bleibt über dem Implementierungsstil und verweist auf API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsdetails erst nach der Stilentscheidung.", - "station.capability-solution-interaction-design.apply_in_work": "", - "station.capability-solution-interaction-design.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "station.capability-solution-interaction-design.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "station.capability-solution-interaction-design.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "station.capability-solution-interaction-design.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.capability-solution-interaction-design.how_it_works": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "station.capability-solution-interaction-design.how_it_works.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "station.capability-solution-interaction-design.how_it_works.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "station.capability-solution-interaction-design.how_it_works.3": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "station.capability-delivery-operations.title": "Capability Delivery & Operations", - "station.capability-delivery-operations.description": "Capability Delivery & Operations klärt Fähigkeit, Consumer, Producer, Serviceerwartungen, Risiken, Nachweise und nächste Entscheidungen auf wiederverwendbarer Ebene.", - "station.capability-delivery-operations.why_it_matters": "Die Capability Cycle bleibt über dem Implementierungsstil und verweist auf API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsdetails erst nach der Stilentscheidung.", - "station.capability-delivery-operations.apply_in_work": "", - "station.capability-delivery-operations.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "station.capability-delivery-operations.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "station.capability-delivery-operations.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "station.capability-delivery-operations.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.capability-delivery-operations.how_it_works": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "station.capability-delivery-operations.how_it_works.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "station.capability-delivery-operations.how_it_works.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "station.capability-delivery-operations.how_it_works.3": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "station.capability-readiness-assurance.title": "Capability Readiness Assurance", - "station.capability-readiness-assurance.description": "Capability Readiness Assurance klärt Fähigkeit, Consumer, Producer, Serviceerwartungen, Risiken, Nachweise und nächste Entscheidungen auf wiederverwendbarer Ebene.", - "station.capability-readiness-assurance.why_it_matters": "Die Capability Cycle bleibt über dem Implementierungsstil und verweist auf API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsdetails erst nach der Stilentscheidung.", - "station.capability-readiness-assurance.apply_in_work": "", - "station.capability-readiness-assurance.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "station.capability-readiness-assurance.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "station.capability-readiness-assurance.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "station.capability-readiness-assurance.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.capability-readiness-assurance.how_it_works": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "station.capability-readiness-assurance.how_it_works.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "station.capability-readiness-assurance.how_it_works.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "station.capability-readiness-assurance.how_it_works.3": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "station.capability-publishing-enablement.title": "Capability Publishing & Enablement", - "station.capability-publishing-enablement.description": "Capability Publishing & Enablement klärt Fähigkeit, Consumer, Producer, Serviceerwartungen, Risiken, Nachweise und nächste Entscheidungen auf wiederverwendbarer Ebene.", - "station.capability-publishing-enablement.why_it_matters": "Die Capability Cycle bleibt über dem Implementierungsstil und verweist auf API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsdetails erst nach der Stilentscheidung.", - "station.capability-publishing-enablement.apply_in_work": "", - "station.capability-publishing-enablement.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "station.capability-publishing-enablement.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "station.capability-publishing-enablement.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "station.capability-publishing-enablement.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.capability-publishing-enablement.how_it_works": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "station.capability-publishing-enablement.how_it_works.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "station.capability-publishing-enablement.how_it_works.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "station.capability-publishing-enablement.how_it_works.3": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde.", - "station.capability-monitoring-improvement.title": "Capability Monitoring & Improvement", - "station.capability-monitoring-improvement.description": "Capability Monitoring & Improvement klärt Fähigkeit, Consumer, Producer, Serviceerwartungen, Risiken, Nachweise und nächste Entscheidungen auf wiederverwendbarer Ebene.", - "station.capability-monitoring-improvement.why_it_matters": "Die Capability Cycle bleibt über dem Implementierungsstil und verweist auf API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsdetails erst nach der Stilentscheidung.", - "station.capability-monitoring-improvement.apply_in_work": "", - "station.capability-monitoring-improvement.outcomes": "Dokumentierte Capability-Entscheidung oder Arbeitsgrundlage", - "station.capability-monitoring-improvement.outcomes.1": "Consumer, Producer, Owner, Nachweise, Randbedingungen und Serviceerwartungen geklärt", - "station.capability-monitoring-improvement.outcomes.2": "Risiken, Annahmen, nächste Schritte und Lifecycle-Auswirkungen sichtbar", - "station.capability-monitoring-improvement.outcomes.3": "Ergebnisse für die nächste Station vorbereitet", - "station.capability-monitoring-improvement.how_it_works": "Klären Sie Zweck, Consumer, Producer, Umfang und Nachweise der Fähigkeit.", - "station.capability-monitoring-improvement.how_it_works.1": "Dokumentieren Sie Entscheidungen, Verantwortlichkeiten, Serviceerwartungen, Risiken und benötigte Artefakte.", - "station.capability-monitoring-improvement.how_it_works.2": "Nutzen Sie das Ergebnis für Architektur, Design, Lieferung, Readiness, Veröffentlichung oder Verbesserung.", - "station.capability-monitoring-improvement.how_it_works.3": "Nutzen Sie API-, Integrations-, Workflow-, Datenprodukt- oder Applikationsguidance erst, nachdem der Implementierungsstil gewählt wurde." + "station.monitoring-and-improving.how_it_works.3": "Lernen und Lifecycle-Entscheidung: Welche Hypothesenannahmen wurden bestätigt oder verworfen, und sollte die Lösung verbessert, erweitert, eingeschränkt, neu gestaltet, pausiert oder stillgelegt werden?" } diff --git a/src/data/method/en/labels.stations.json b/src/data/method/en/labels.stations.json index 6761b70..fd2dbcf 100644 --- a/src/data/method/en/labels.stations.json +++ b/src/data/method/en/labels.stations.json @@ -67,7 +67,7 @@ "station.api-audit.title": "Quality & Readiness Assurance", "station.api-audit.description": "Review release readiness using evidence from design, testing, operations, permissions, monitoring, support, fallback, rollback, risk, and ownership before production use.", "station.api-audit.why_it_matters": "A formal readiness decision prevents automation solutions from being released without clear evidence, accepted risks, remediation actions, and business and operational ownership.", - "station.api-audit.apply_in_work": "", + "station.api-audit.apply_in_work": "Use readiness evidence to make an explicit go, conditional-go, or no-go decision before production use.", "station.api-audit.outcomes": "Formal readiness decision", "station.api-audit.outcomes.1": "Evidence, blocking findings, accepted residual risks, and remediation actions reviewed", "station.api-audit.outcomes.2": "Release decision recorded as ready, ready with conditions, remediation required, or not approved", @@ -78,7 +78,7 @@ "station.api-publishing.title": "Publishing & Enablement", "station.api-publishing.description": "Enable released solutions so users, operators, affected teams, consuming systems, service consumers, and support teams can adopt them safely.", "station.api-publishing.why_it_matters": "Automation solutions only create value after rollout when affected people and consuming systems understand what changes, how access and operation work, where to get support, and when rollout should pause, expand, or roll back.", - "station.api-publishing.apply_in_work": "", + "station.api-publishing.apply_in_work": "Plan rollout, enablement, support, feedback, and rollback so released solutions can be adopted safely.", "station.api-publishing.outcomes": "Safe rollout and enablement plan", "station.api-publishing.outcomes.1": "Affected people, changed responsibilities, decisions, handoffs, and working practices understood", "station.api-publishing.outcomes.2": "Activation, access, permissions, rollout approach, enablement, and support prepared", @@ -89,7 +89,7 @@ "station.monitoring-and-improving.title": "Monitoring & Improvement", "station.monitoring-and-improving.description": "Monitor actual outcomes, operational performance, user behavior, risk, recovery, realized value, and improvement opportunities after release.", "station.monitoring-and-improving.why_it_matters": "Released solutions need evidence to show whether expected outcomes are being achieved, where manual intervention or recovery is still needed, and what lifecycle decision should be made next.", - "station.monitoring-and-improving.apply_in_work": "", + "station.monitoring-and-improving.apply_in_work": "Use operational, user, risk, and value evidence to decide what to improve, expand, restrict, pause, or retire.", "station.monitoring-and-improving.outcomes": "Measured outcome, performance, risk, recovery, and value evidence", "station.monitoring-and-improving.outcomes.1": "Expected outcomes, run performance, user behavior, risks, support needs, and realized value reviewed", "station.monitoring-and-improving.outcomes.2": "Hypothesis assumptions and lifecycle options assessed", @@ -468,205 +468,5 @@ "station.api-audit.how_it_works.4": "Record the decision owner, decision date, and evidence used.", "station.api-audit.how_it_works.5": "Confirm that nothing proceeds to release without clear business and operational ownership.", "station.api-publishing.how_it_works.3": "Feedback and control: How will adoption, trust, actual use, issues, and unexpected behavior be monitored, and what conditions trigger pause, rollback, or return to manual operation?", - "station.monitoring-and-improving.how_it_works.3": "Learning and lifecycle decision: Which hypothesis assumptions were supported or rejected, and should the solution be improved, expanded, restricted, redesigned, paused, or retired?", - "station.integration-capability-strategy.title": "Integration Capability Strategy", - "station.integration-capability-strategy.description": "Prioritize a reusable integration capability hypothesis before choosing the implementation style. Use supporting canvases only where the necessary evidence does not already exist.", - "station.integration-capability-strategy.why_it_matters": "Integration work often jumps too quickly to a technical pattern. This station keeps the team focused on consumer need, value, domain meaning, ownership, reuse potential, viability, assumptions, and validation before selecting APIs, events, files, streams, data products, direct integration, or hybrids.", - "station.integration-capability-strategy.apply_in_work": "Use the Integration Capability Hypothesis Canvas as the primary artifact; reference Customer Journey, Domain, Capability Value Proposition, Capability Business Model, Business Impact, and Capacity canvases only as optional supporting evidence.", - "station.integration-capability-strategy.outcomes": "A testable integration capability hypothesis", - "station.integration-capability-strategy.outcomes.1": "Consumers, reuse scope, provider, owner, and supporting evidence clarified", - "station.integration-capability-strategy.outcomes.2": "Critical assumptions, validation step, and proceed-or-stop decision documented", - "station.integration-capability-strategy.outcomes.3": "Optional supporting canvases identified as evidence, not mandatory work", - "station.integration-capability-strategy.how_it_works": "State the reusable integration capability hypothesis and intended outcome.", - "station.integration-capability-strategy.how_it_works.1": "Identify intended consumers, reuse scope, provider, owner, and optional supporting evidence.", - "station.integration-capability-strategy.how_it_works.2": "Record the initial implementation-style hypothesis without treating it as an architecture decision.", - "station.integration-capability-strategy.how_it_works.3": "Define critical assumptions, smallest validation experiment, and proceed-or-stop decision.", - "station.integration-consumer-requirements-onboarding.title": "Integration Consumer Requirements & Onboarding", - "station.integration-consumer-requirements-onboarding.description": "Capture integration consumer and provider requirements, onboarding needs, service expectations, data quality, support, and recovery requirements.", - "station.integration-consumer-requirements-onboarding.why_it_matters": "The right architecture depends on consumer systems, provider responsibilities, data needs, access, environments, credentials, compatibility, observability, support, failure handling, replay, reconciliation, and recovery expectations.", - "station.integration-consumer-requirements-onboarding.apply_in_work": "Use consumer and provider requirements to make expectations explicit before architecture selection.", - "station.integration-consumer-requirements-onboarding.outcomes": "Documented consumer and provider requirements", - "station.integration-consumer-requirements-onboarding.outcomes.1": "Consumer systems, provider responsibilities, and onboarding needs clarified", - "station.integration-consumer-requirements-onboarding.outcomes.2": "Service, data quality, support, and recovery expectations documented", - "station.integration-consumer-requirements-onboarding.outcomes.3": "Architecture-relevant constraints ready for decision making", - "station.integration-consumer-requirements-onboarding.how_it_works": "Identify consumer systems and teams, provider responsibilities, interaction needs, data needs, onboarding, and access expectations.", - "station.integration-consumer-requirements-onboarding.how_it_works.1": "Define environments, test access, credentials, identity, compatibility, versioning, and service expectations.", - "station.integration-consumer-requirements-onboarding.how_it_works.2": "Capture data quality, observability, support, failure handling, replay, reconciliation, and recovery needs.", - "station.integration-consumer-requirements-onboarding.how_it_works.3": "Keep API onboarding resources conditional for API-based implementations.", - "station.integration-architecture-platform-decisions.title": "Integration Architecture & Platform Decisions", - "station.integration-architecture-platform-decisions.description": "Select the integration architecture, implementation style, platform capabilities, and governance model from evidence.", - "station.integration-architecture-platform-decisions.why_it_matters": "Architecture choices should follow from evidence about timing, coupling, data ownership, consistency, reliability, replay, latency, volume, security, maintainability, observability, platform fit, cost, governance, vendor dependency, and skills.", - "station.integration-architecture-platform-decisions.apply_in_work": "Use the Integration Architecture Decision Canvas as the primary decision artifact.", - "station.integration-architecture-platform-decisions.outcomes": "A justified integration architecture decision", - "station.integration-architecture-platform-decisions.outcomes.1": "Selected style or hybrid and platform decision documented", - "station.integration-architecture-platform-decisions.outcomes.2": "Rejected alternatives, risks, assumptions, and supporting evidence recorded", - "station.integration-architecture-platform-decisions.outcomes.3": "Conditional inputs such as Business Impact, Location, and Capacity linked where relevant", - "station.integration-architecture-platform-decisions.how_it_works": "Compare candidate styles such as API, event, messaging, file, stream, ETL/ELT, data product, direct database, managed connector, point-to-point, custom, shared platform, or hybrid.", - "station.integration-architecture-platform-decisions.how_it_works.1": "Evaluate candidates using timing, coupling, data ownership, consistency, reliability, delivery guarantees, replay, latency, volume, security, maintainability, observability, platform fit, cost, governance, vendor dependency, and skills.", - "station.integration-architecture-platform-decisions.how_it_works.2": "Record the selected style or hybrid, platform decision, rationale, rejected alternatives, open risks, and assumptions.", - "station.integration-architecture-platform-decisions.how_it_works.3": "Use Location, Business Impact, and Capacity canvases only as conditional inputs: location for regulatory, network, residency, or trust-boundary constraints; business impact for criticality, investment, or risk; capacity for volume, timing, load, or scale.", - "station.integration-solution-design.title": "Integration Solution Design", - "station.integration-solution-design.description": "Design the integration solution, contracts, schemas, data structures, mappings, and interaction or delivery patterns for the selected style.", - "station.integration-solution-design.why_it_matters": "Once the architecture pattern is known, design work should use only the artifacts that fit the selected style rather than treating REST, Event, and GraphQL as mandatory for every integration.", - "station.integration-solution-design.apply_in_work": "Select design resources that fit the chosen implementation style and document the integration contract before implementation.", - "station.integration-solution-design.outcomes": "A validated integration solution design for the selected style", - "station.integration-solution-design.outcomes.1": "Contracts, schemas, mappings, examples, lifecycle rules, and consumer obligations documented", - "station.integration-solution-design.outcomes.2": "Design traceability back to requirements and architecture decisions", - "station.integration-solution-design.outcomes.3": "Style-specific design resources selected only where relevant", - "station.integration-solution-design.how_it_works": "Start from the selected architecture decision and use the Integration Solution Design Canvas as the primary cross-style design summary.", - "station.integration-solution-design.how_it_works.1": "Document producer and consumer boundaries, contracts, schemas, mappings, transformations, delivery pattern, identity, security, error model, retry, replay, correlation, reconciliation, observability, and versioning.", - "station.integration-solution-design.how_it_works.2": "Use Interaction Canvas and style-specific design resources only for deeper design of REST, GraphQL, event, messaging, file, stream, data product, direct integration, connector, B2B/EDI, webhook, orchestration, or hybrid implementation.", - "station.integration-solution-design.how_it_works.3": "Apply contract-first integration design using OpenAPI, AsyncAPI, event schemas, message schemas, file schemas, data contracts, or interface specifications where useful.", - "station.integration-delivery-operations.title": "Integration Delivery & Operations", - "station.integration-delivery-operations.description": "Build, test, deploy, and operate the integration capability using its selected implementation style and validated contract.", - "station.integration-delivery-operations.why_it_matters": "A reusable integration capability needs reliable delivery and operations regardless of whether it uses APIs, events, messages, files, streams, data products, connectors, or direct integration.", - "station.integration-delivery-operations.apply_in_work": "Use integration delivery, testing, CI/CD, security, recovery, reconciliation, and operations guidance for the chosen style.", - "station.integration-delivery-operations.outcomes": "A delivered integration capability aligned with the validated contract", - "station.integration-delivery-operations.outcomes.1": "Testing, deployment, security, operations, recovery, and reconciliation evidence prepared", - "station.integration-delivery-operations.outcomes.2": "Ownership, environments, monitoring, support, and readiness status documented", - "station.integration-delivery-operations.outcomes.3": "Traceable delivery and release controls", - "station.integration-delivery-operations.how_it_works": "Implement the validated contract and architecture decision using appropriate code, configuration, connectors, mappings, schemas, and platform standards.", - "station.integration-delivery-operations.how_it_works.1": "Test functionality, contracts, schemas, mappings, compatibility, data quality, security, performance, resilience, replay, reconciliation, and recovery.", - "station.integration-delivery-operations.how_it_works.2": "Automate build, validation, deployment, configuration, migration, release, rollback, and traceability.", - "station.integration-delivery-operations.how_it_works.3": "Protect identities, credentials, data, trust boundaries, access, privacy, auditability, and platform controls.", - "station.integration-delivery-operations.how_it_works.4": "Prepare retry, replay, duplicate handling, ordering, dead-lettering, restartability, reconciliation, fallback, compensation, and rollback.", - "station.integration-delivery-operations.how_it_works.5": "Record ownership, environments, evidence, known risks, support, monitoring, and readiness status in the Integration Readiness & Operations Canvas.", - "station.integration-readiness-assurance.title": "Integration Readiness Assurance", - "station.integration-readiness-assurance.description": "Review integration readiness using evidence from contracts, schemas, mappings, testing, operations, environments, permissions, monitoring, support, recovery, risk, and ownership before release.", - "station.integration-readiness-assurance.why_it_matters": "A formal readiness decision prevents integration capabilities from being released without validated contracts, operational evidence, accepted risks, and clear producer, consumer, and operational ownership.", - "station.integration-readiness-assurance.apply_in_work": "", - "station.integration-readiness-assurance.outcomes": "Formal integration readiness decision", - "station.integration-readiness-assurance.outcomes.1": "Evidence, blocking findings, accepted residual risks, release conditions, and remediation actions reviewed", - "station.integration-readiness-assurance.outcomes.2": "Release decision recorded as ready, ready with conditions, remediation required, or not approved", - "station.integration-readiness-assurance.outcomes.3": "Producer, consumer, platform, business, and operational ownership confirmed", - "station.integration-readiness-assurance.how_it_works": "Review interface contracts, schemas, mappings, test evidence, environments, permissions, credentials, monitoring, support, replay, reconciliation, fallback, and recovery arrangements.", - "station.integration-readiness-assurance.how_it_works.1": "Verify compatibility, data quality, security, privacy, compliance, performance, resilience, delivery guarantees, ordering, duplication, error handling, producer and consumer deployment sequencing, migration, cutover, and backward compatibility.", - "station.integration-readiness-assurance.how_it_works.2": "Confirm producer, consumer, platform, business, and operational ownership.", - "station.integration-readiness-assurance.how_it_works.3": "Record blocking findings, accepted residual risks, release conditions, and remediation actions.", - "station.integration-readiness-assurance.how_it_works.4": "Decide whether the release is ready, ready with conditions, requires remediation, or is not approved.", - "station.integration-readiness-assurance.how_it_works.5": "Record decision owner, date, and evidence.", - "station.integration-publishing-enablement.title": "Integration Publishing & Enablement", - "station.integration-publishing-enablement.description": "Publish the integration capability so current and future consumers can discover it, understand it, request access, complete onboarding, reuse it, and get support.", - "station.integration-publishing-enablement.why_it_matters": "Integration capabilities create reuse value only when consumers can discover them, understand their contracts and service expectations, complete onboarding, operate them reliably, and receive support throughout the lifecycle.", - "station.integration-publishing-enablement.apply_in_work": "", - "station.integration-publishing-enablement.outcomes": "Published integration capability ready for reuse", - "station.integration-publishing-enablement.outcomes.1": "Audience, discovery location, ownership, lifecycle status, contracts, schemas, examples, dependencies, and limitations published", - "station.integration-publishing-enablement.outcomes.2": "Access, credentials, test environments, onboarding, support, service expectations, and governance paths defined", - "station.integration-publishing-enablement.outcomes.3": "Versioning, deprecation, migration, compatibility, feedback, and lifecycle communication prepared", - "station.integration-publishing-enablement.how_it_works": "Discovery and audience: Who are the intended current and future consumers, and where should the integration capability be discoverable?", - "station.integration-publishing-enablement.how_it_works.1": "Published information: What purpose, ownership, lifecycle status, contracts, schemas, service expectations, dependencies, examples, and limitations must be published?", - "station.integration-publishing-enablement.how_it_works.2": "Access, onboarding, reuse, validation, and support: How do consumers request access, obtain credentials, access sandbox or test environments, validate connectivity, run contract tests or conformance checks, follow governance, and get support?", - "station.integration-publishing-enablement.how_it_works.3": "Release, migration, and feedback: How are versions, deprecation, migration, compatibility, retirement, issues, improvement requests, and adoption evidence handled?", - "station.integration-monitoring-improvement.title": "Integration Monitoring & Improvement", - "station.integration-monitoring-improvement.description": "Monitor integration reliability, performance, capacity, data quality, consumer experience, reuse, cost, operability, value, and lifecycle improvement needs.", - "station.integration-monitoring-improvement.why_it_matters": "Released integration capabilities need evidence to show whether they are reliable, reusable, valuable, supportable, and still architecturally fit for their consumers.", - "station.integration-monitoring-improvement.apply_in_work": "", - "station.integration-monitoring-improvement.outcomes": "Integration reliability, value, adoption, and lifecycle evidence", - "station.integration-monitoring-improvement.outcomes.1": "Reliability, performance, capacity, recovery, and data quality metrics reviewed", - "station.integration-monitoring-improvement.outcomes.2": "Consumer experience, reuse, adoption, cost, operability, and value evidence assessed", - "station.integration-monitoring-improvement.outcomes.3": "Lifecycle decisions and improvement backlog informed by integration evidence", - "station.integration-monitoring-improvement.how_it_works": "Reliability: What do availability, success rate, failure rate, retries, dead-lettering, replay, duplication, ordering, timeout, and recovery metrics show?", - "station.integration-monitoring-improvement.how_it_works.1": "Performance, capacity, and data quality: What do latency, throughput, queue depth, stream lag, batch duration, file-delivery time, peak load, schema violations, mapping errors, missing data, stale data, and reconciliation differences show?", - "station.integration-monitoring-improvement.how_it_works.2": "Consumer experience, reuse, cost, and operability: Are consumers discovering, onboarding, integrating, operating, receiving support, and reusing the capability without fragmentation, deprecated-version buildup, unowned integrations, or excessive cost?", - "station.integration-monitoring-improvement.how_it_works.3": "Lifecycle and learning: Should the integration be improved, scaled, standardized, consolidated, versioned, deprecated, replaced, or retired, and which architecture or reuse assumptions were supported or rejected?", - "station.capability-strategy.title": "Capability Strategy", - "station.capability-strategy.description": "Prioritize a reusable digital capability hypothesis by linking consumer, value, domain, ownership, viability, and reuse evidence to a clear scope, assumptions, validation step, and decision. Use supporting canvases only where the necessary evidence does not already exist.", - "station.capability-strategy.why_it_matters": "A capability cycle should answer what reusable digital capability should exist, for whom, why, and under what operating model before selecting a delivery style.", - "station.capability-strategy.apply_in_work": "Use the Capability Hypothesis Canvas to decide whether the capability deserves further productization.", - "station.capability-strategy.outcomes": "A testable capability hypothesis", - "station.capability-strategy.outcomes.1": "Target consumers, use cases, reusable scope, evidence, outcomes, and owner clarified", - "station.capability-strategy.outcomes.2": "Critical assumptions, validation step, and proceed, revise, or reject decision documented", - "station.capability-strategy.outcomes.3": "Optional supporting canvases identified as evidence, not mandatory work", - "station.capability-strategy.how_it_works": "State the reusable capability hypothesis and expected consumer or business outcome.", - "station.capability-strategy.how_it_works.1": "Identify target consumers, use cases, reusable scope, owner, and optional supporting evidence.", - "station.capability-strategy.how_it_works.2": "Link journey, value, domain, business-model, business-impact, or capacity evidence only where needed.", - "station.capability-strategy.how_it_works.3": "Record assumptions, minimum validation, and decision.", - "station.capability-consumer-producer-requirements.title": "Consumer, Producer & Service Requirements", - "station.capability-consumer-producer-requirements.description": "Capture intended consumers, consuming contexts, capability owner and producer responsibilities, discovery, access, service, quality, support, lifecycle, operational, and governance requirements.", - "station.capability-consumer-producer-requirements.why_it_matters": "Reusable capabilities succeed when consumer needs and producer commitments are explicit before implementation style and platform decisions.", - "station.capability-consumer-producer-requirements.apply_in_work": "Use the requirements canvas to make consumer expectations and producer commitments explicit.", - "station.capability-consumer-producer-requirements.outcomes": "Documented consumer, producer, and service requirements", - "station.capability-consumer-producer-requirements.outcomes.1": "Consumers, consuming contexts, producer commitments, and access expectations clarified", - "station.capability-consumer-producer-requirements.outcomes.2": "Service quality, availability, support, lifecycle, and governance expectations documented", - "station.capability-consumer-producer-requirements.outcomes.3": "Architecture-relevant constraints ready for decision making", - "station.capability-consumer-producer-requirements.how_it_works": "Identify intended consumers, consuming contexts, capability owner, producer responsibilities, and producer commitments.", - "station.capability-consumer-producer-requirements.how_it_works.1": "Capture discovery, evaluation, access, onboarding, service, quality, availability, change, and lifecycle expectations.", - "station.capability-consumer-producer-requirements.how_it_works.2": "Record support, incident communication, consumer responsibilities, operational constraints, and governance constraints.", - "station.capability-consumer-producer-requirements.how_it_works.3": "Keep API onboarding resources conditional for API-based implementations.", - "station.capability-architecture-platform-decisions.title": "Capability Architecture & Platform Decisions", - "station.capability-architecture-platform-decisions.description": "Select the capability implementation style, architecture pattern, enabling platform, and governance model from evidence.", - "station.capability-architecture-platform-decisions.why_it_matters": "Capability architecture should follow evidence about consumer needs, reuse, coupling, latency, timing, volume, data ownership, consistency, security, trust boundaries, reliability, operability, cost, skills, platform fit, governance, discoverability, and lifecycle management.", - "station.capability-architecture-platform-decisions.apply_in_work": "Use the architecture decision canvas to select and justify the implementation style and platform.", - "station.capability-architecture-platform-decisions.outcomes": "A justified capability architecture decision", - "station.capability-architecture-platform-decisions.outcomes.1": "Selected implementation style and enabling platform documented", - "station.capability-architecture-platform-decisions.outcomes.2": "Rejected alternatives, assumptions, risks, and decision rationale recorded", - "station.capability-architecture-platform-decisions.outcomes.3": "Business Impact, Location, and Capacity linked only as conditional inputs", - "station.capability-architecture-platform-decisions.how_it_works": "Use the candidate status control to compare API, event, file or batch, stream, data product, workflow, shared service, user-facing application, direct integration, platform-native feature, human-assisted service, and hybrid options.", - "station.capability-architecture-platform-decisions.how_it_works.1": "Evaluate candidates against consumer needs, reuse potential, coupling, latency, timing, volume, data ownership, consistency, security, trust boundaries, reliability, operability, cost, skills, platform fit, governance, discoverability, and lifecycle management.", - "station.capability-architecture-platform-decisions.how_it_works.2": "Record selected implementation style, enabling platform, rationale, rejected alternatives, assumptions, and risks.", - "station.capability-architecture-platform-decisions.how_it_works.3": "Use Business Impact, Location, and Capacity only where criticality, boundaries, demand, load, or scale materially affect the decision.", - "station.capability-solution-interaction-design.title": "Capability Solution & Interaction Design", - "station.capability-solution-interaction-design.description": "Design how consumers access, interact with, receive, or use the capability through the selected implementation style.", - "station.capability-solution-interaction-design.why_it_matters": "A capability may become an API, workflow, application, data product, shared service, human-assisted service, integration, or hybrid model, so design must cover more than interface contracts.", - "station.capability-solution-interaction-design.apply_in_work": "Use the solution design canvas to describe how consumers will access, interact with, receive, or use the capability.", - "station.capability-solution-interaction-design.outcomes": "Capability solution and interaction design", - "station.capability-solution-interaction-design.outcomes.1": "Service boundary, interaction model, data and business concepts, contracts or service definitions documented", - "station.capability-solution-interaction-design.outcomes.2": "Responsibilities, rules, inputs, outputs, exceptions, lifecycle, security, privacy, observability, and support model clarified", - "station.capability-solution-interaction-design.outcomes.3": "Design traceable to requirements and architecture decisions", - "station.capability-solution-interaction-design.how_it_works": "Start from the selected implementation style and define the capability service boundary.", - "station.capability-solution-interaction-design.how_it_works.1": "Design the consumer interaction model, data and business concepts, contract or service definition, responsibilities, rules, inputs, and outputs.", - "station.capability-solution-interaction-design.how_it_works.2": "Define errors, exceptions, lifecycle, versioning, security, privacy, observability, and support model.", - "station.capability-solution-interaction-design.how_it_works.3": "Use contract-first capability design where API contracts, event schemas, file schemas, data contracts, service agreements, workflow inputs and outputs, or user-facing service promises need validation.", - "station.capability-delivery-operations.title": "Capability Delivery & Operations", - "station.capability-delivery-operations.description": "Deliver and operate the reusable capability using implementation-style-appropriate engineering, testing, security, release, support, and operational ownership practices.", - "station.capability-delivery-operations.why_it_matters": "A reusable capability needs reliable delivery and operations whether it becomes a workflow, application, data product, shared service, human-assisted service, integration, API, or hybrid capability.", - "station.capability-delivery-operations.apply_in_work": "Use the operations canvas to prepare delivery evidence, ownership, support, continuity, and readiness status.", - "station.capability-delivery-operations.outcomes": "Delivered capability with prepared operating model", - "station.capability-delivery-operations.outcomes.1": "Testing, validation, release, security, access, support, and lifecycle evidence prepared", - "station.capability-delivery-operations.outcomes.2": "Business, capability, producer, operational, and support ownership documented", - "station.capability-delivery-operations.outcomes.3": "Readiness status, risks, fallback, documentation, and improvement backlog visible", - "station.capability-delivery-operations.how_it_works": "Implement or configure the capability from the validated design and selected implementation style.", - "station.capability-delivery-operations.how_it_works.1": "Validate functionality, service expectations, data quality, security, compatibility, resilience, consumer impact, and support readiness.", - "station.capability-delivery-operations.how_it_works.2": "Prepare release controls, environments, permissions, credentials, monitoring, support, fallback, change ownership, documentation, runbooks, known risks, and improvement backlog.", - "station.capability-delivery-operations.how_it_works.3": "Use style-specific delivery guidance only after the implementation style is selected.", - "station.capability-delivery-operations.how_it_works.4": "Record the operating model in the Capability Readiness & Operations Canvas.", - "station.capability-delivery-operations.how_it_works.5": "Leave the formal release decision to Readiness Assurance.", - "station.capability-readiness-assurance.title": "Capability Readiness Assurance", - "station.capability-readiness-assurance.description": "Review capability readiness using evidence from solution design, contract or service definition, testing, operations, permissions, monitoring, support, fallback, lifecycle, risk, and ownership before release.", - "station.capability-readiness-assurance.why_it_matters": "A formal readiness decision prevents reusable capabilities from being released without clear evidence, accepted risks, consumer and operational commitments, and accountable ownership.", - "station.capability-readiness-assurance.apply_in_work": "", - "station.capability-readiness-assurance.outcomes": "Formal capability readiness decision", - "station.capability-readiness-assurance.outcomes.1": "Evidence, blocking findings, residual risks, release conditions, and remediation actions reviewed", - "station.capability-readiness-assurance.outcomes.2": "Release decision recorded as ready, ready with conditions, remediation required, or not approved", - "station.capability-readiness-assurance.outcomes.3": "Business, capability, producer, and operational ownership confirmed", - "station.capability-readiness-assurance.how_it_works": "Review the completed solution design, contract or service definition, test evidence, operating model, permissions, monitoring, support, fallback, and lifecycle arrangements.", - "station.capability-readiness-assurance.how_it_works.1": "Verify that business, operational, security, privacy, compliance, data quality, compatibility, resilience, and consumer-impact risks have been addressed or accepted.", - "station.capability-readiness-assurance.how_it_works.2": "Confirm clear business, capability, producer, and operational ownership.", - "station.capability-readiness-assurance.how_it_works.3": "Record blocking findings, residual risks, release conditions, and remediation actions.", - "station.capability-readiness-assurance.how_it_works.4": "Decide whether the capability is ready, ready with conditions, requires remediation, or is not approved.", - "station.capability-readiness-assurance.how_it_works.5": "Record the decision owner, date, and evidence.", - "station.capability-publishing-enablement.title": "Capability Publishing & Enablement", - "station.capability-publishing-enablement.description": "Publish the reusable capability so intended consumers can discover it, understand its purpose and service expectations, request access, onboard, use it, and get support.", - "station.capability-publishing-enablement.why_it_matters": "Reusable capabilities create value only when consumers can discover them, understand their purpose and service expectations, access them, use them successfully, and receive support throughout the lifecycle.", - "station.capability-publishing-enablement.apply_in_work": "", - "station.capability-publishing-enablement.outcomes": "Published capability ready for consumer use", - "station.capability-publishing-enablement.outcomes.1": "Audience, discovery location, purpose, value, ownership, lifecycle status, usage conditions, examples, limitations, and dependencies published", - "station.capability-publishing-enablement.outcomes.2": "Access, onboarding, service expectations, governance, support, feedback, versioning, migration, deprecation, and retirement paths defined", - "station.capability-publishing-enablement.outcomes.3": "Consumer evaluation and validation path available", - "station.capability-publishing-enablement.how_it_works": "Audience and discovery: who are the intended consumers, and where should the capability be discoverable?", - "station.capability-publishing-enablement.how_it_works.1": "Published information: what purpose, value, ownership, lifecycle status, usage conditions, contracts, examples, limitations, and dependencies must be published?", - "station.capability-publishing-enablement.how_it_works.2": "Access, onboarding, service expectations, governance, and support: how do consumers evaluate, request, access, test, begin using, get help, report issues, and request improvements?", - "station.capability-publishing-enablement.how_it_works.3": "Versioning and retirement: how are changes, migration, deprecation, and retirement handled?", - "station.capability-monitoring-improvement.title": "Capability Monitoring & Improvement", - "station.capability-monitoring-improvement.description": "Monitor capability value, outcomes, adoption, reuse, service health, consumer experience, cost, sustainability, and lifecycle improvement needs.", - "station.capability-monitoring-improvement.why_it_matters": "Capabilities should continue only when they create value, reduce friction, avoid duplication, remain supportable, and have sustainable ownership and funding.", - "station.capability-monitoring-improvement.apply_in_work": "", - "station.capability-monitoring-improvement.outcomes": "Capability value, adoption, reuse, service health, and lifecycle evidence", - "station.capability-monitoring-improvement.outcomes.1": "Consumer and business outcomes, friction, duplication, cost, risk, and delay reviewed", - "station.capability-monitoring-improvement.outcomes.2": "Adoption, reuse, support, incidents, consumer experience, funding, and ownership sustainability assessed", - "station.capability-monitoring-improvement.outcomes.3": "Lifecycle decision and improvement backlog informed by evidence", - "station.capability-monitoring-improvement.how_it_works": "Value and outcomes: are expected consumer and business outcomes being achieved, and is the capability reducing friction, duplication, cost, risk, or delay?", - "station.capability-monitoring-improvement.how_it_works.1": "Adoption and reuse: which consumers and use cases are using it, is reuse increasing, and are teams creating duplicates instead?", - "station.capability-monitoring-improvement.how_it_works.2": "Service health and consumer experience: are availability, quality, timeliness, support, change expectations, discovery, evaluation, onboarding, use, and feedback working effectively?", - "station.capability-monitoring-improvement.how_it_works.3": "Cost, sustainability, and lifecycle: should the capability be improved, expanded, consolidated, standardized, replaced, deprecated, or retired, and which original assumptions were supported or rejected?" + "station.monitoring-and-improving.how_it_works.3": "Learning and lifecycle decision: Which hypothesis assumptions were supported or rejected, and should the solution be improved, expanded, restricted, redesigned, paused, or retired?" } diff --git a/src/data/method/fi/labels.criteria.json b/src/data/method/fi/labels.criteria.json index 7be1594..d43ff28 100644 --- a/src/data/method/fi/labels.criteria.json +++ b/src/data/method/fi/labels.criteria.json @@ -23,11 +23,11 @@ "criterion.api-documentation-ready": "Hyödyntäjille suunnattu dokumentaatio ja käyttöönottomateriaalit ovat valmiit.", "criterion.consumer-support-ready": "Hyödyntäjien käyttöönotto-, tuki- ja viestintäprosessit ovat valmiit.", "criterion.legal-compliance-clear": "Julkaisun tai toimituksen oikeudelliset, tietosuoja- ja vaatimustenmukaisuusvaatimukset on määritelty ja ymmärretty.", - "criterion.automation-opportunity-evidence-ready": "The automation hypothesis has enough referenced evidence about expected outcome, scope, initial implementation assumptions, critical risks, validation experiment, thresholds, and decision to determine whether it should proceed.", - "criterion.automation-owner-confirmed": "Ownership is clear for the automation opportunity, process decisions, PoC validation, risks, and lifecycle outcomes.", - "criterion.automation-architecture-and-controls-validated": "The selected automation architecture, implementation mechanisms, human controls, security constraints, and recovery approach have been validated with the relevant stakeholders.", - "criterion.automation-operational-readiness-confirmed": "The automation has evidence for functional correctness, permissions, exception handling, oversight, monitoring, support, rollback, and operational ownership.", - "criterion.automation-value-monitoring-ready": "Automation performance, process outcomes, risk signals, manual interventions, incidents, and realized benefits can be monitored and used to prioritize improvements.", + "criterion.automation-opportunity-evidence-ready": "Automaation hypoteesilla on riittävästi viitattua näyttöä odotetusta tuloksesta, rajauksesta, alkuperäisistä toteutusoletuksista, kriittisistä riskeistä, validointikokeesta, kynnysarvoista ja päätöksestä sen arvioimiseksi, pitäisikö sitä edistää.", + "criterion.automation-owner-confirmed": "Omistajuus on selkeä automaatiomahdollisuudelle, prosessipäätäksille, PoC-validoinnille, riskeille ja elinkaaren tuloksille.", + "criterion.automation-architecture-and-controls-validated": "Valittu automaatioarkkitehtuuri, toteutusmekanismit, ihmisen tekemät kontrollit, tietoturvarajoitteet ja palautumismalli on validoitu olennaisten sidosryhmien kanssa.", + "criterion.automation-operational-readiness-confirmed": "Automaatiolla on näyttöä toiminnallisesta oikeellisuudesta, käyttöoikeuksista, poikkeusten käsittelystä, valvonnasta, seurannasta, tuesta, palautuksesta ja operatiivisesta omistajuudesta.", + "criterion.automation-value-monitoring-ready": "Automaation suorituskykyä, prosessin tuloksia, riskisignaaleja, manuaalisia puuttumisia, häiriöitä ja toteutuneita hyötyjä voidaan seurata ja käyttää parannusten priorisointiin.", "criterion.integration-readiness-confirmed": "Integraatiosopimukset, skeemat, mäppäykset, testinäyttö, ympäristöt, oikeudet, tunnistetiedot, seuranta, tuki, replay, täsmäytys, fallback, palautuminen, riskit ja omistajuus on arvioitu julkaisuvalmiutta varten.", "criterion.integration-published-for-reuse": "Integraatiokyvykkyys on löydettävissä ja sille on julkaistu omistajuus, elinkaaritila, sopimukset, skeemat, palveluodotukset, pääsy- ja onboarding-polut, tuki, versiointi ja palautekanavat.", "criterion.capability-readiness-confirmed": "Kyvykkyyden suunnittelu, palvelumäärittely, testinäyttö, toimintamalli, oikeudet, seuranta, tuki, fallback, elinkaarijärjestelyt, riskit ja omistajuus on arvioitu julkaisuvalmiutta varten.", diff --git a/src/data/method/fi/labels.cycles.json b/src/data/method/fi/labels.cycles.json index 457dbfc..46c835e 100644 --- a/src/data/method/fi/labels.cycles.json +++ b/src/data/method/fi/labels.cycles.json @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "API-julkaisu", "cycle.station.monitoring-and-improving": "APIen seuranta ja parantaminen", "cycle.station.integration-capability-strategy": "Integraatiokyvykkyyden strategia", - "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", + "cycle.station.integration-consumer-requirements-onboarding": "Integraation hyödyntäjän ja tarjoajan sitoumukset", "cycle.station.integration-architecture-decision": "Integraatioarkkitehtuuri ja alustapaatokset", "cycle.station.integration-solution-design": "Integraation ratkaisusuunnittelu", "cycle.station.integration-delivery-operations": "Integraation toimitus ja operointi", @@ -37,20 +37,6 @@ "cycle.owner.api-platform-owner": "API-alustan omistaja", "cycle.owner.integration-architect": "Integraatioarkkitehti", "cycle.owner.solution-architect": "Ratkaisuarkkitehti", - "cycle.template.intent-fit.title": "Tarkoitus ja soveltuvuus", - "cycle.template.intent-fit.description": "Kuvaa liiketoimintatulos, hyödyntäjät, tuottajat, rajaus, rajoitteet ja päätöksen tila.", - "cycle.template.requirements.title": "Vaatimukset", - "cycle.template.requirements.description": "Kokoa asiantuntijoiden syötteet suositeltujen kysymysten avulla. Käsittele vastauksia suunnittelupäätösten lähtötietoina, älä lopullisina suunnittelupäätöksinä.", - "cycle.template.architecture-decision.title": "Arkkitehtuuripäätös", - "cycle.template.architecture-decision.description": "Vertaa mahdollisia arkkitehtuurivalintoja koottuihin vaatimuksiin, näyttöön, riskeihin ja avoimiin kysymyksiin.", - "cycle.template.api-architecture-decision.title": "API-arkkitehtuuripäätös", - "cycle.template.api-architecture-decision.description": "Dokumentoi API-arkkitehtuuria, alustaa, tietoturvaa, elinkaarta ja julkaisua koskevat päätökset.", - "cycle.template.integration-pattern-decision.title": "Integraatiomallin päätös", - "cycle.template.integration-pattern-decision.description": "Vertaa API-, tapahtuma-, tiedosto-, virta-, datatuote-, suora integraatio- ja hybridivaihtoehtoja vaatimuksiin.", - "cycle.template.human-validation.title": "Ihmisen tekemä validointi", - "cycle.template.human-validation.description": "Dokumentoi, kuka validoi tekoälyavusteiset tuotokset ja mitkä päätökset edellyttävät ihmisen vastuuta.", - "cycle.template.adr.title": "Arkkitehtuuripäätöksen dokumentti", - "cycle.template.adr.description": "Kirjaa valittu päätös, perustelut, vaihtoehdot, seuraukset, näyttö ja jatkotoimet.", "cycle.api-productization-cycle.station.api-product-strategy.description": "Miellä API tuotteena, jolla on selkeä arvolupaus, hyödyntäjät, liiketoimintamalli, omistajuus ja elinkaaren tavoite.", "cycle.api-productization-cycle.station.api-consumer-experience.description": "Määrittele API-hyödyntäjäsegmentit, käyttöönoton polut, odotukset ja kokemukseen liittyvät vaatimukset ennen suunnittelupäätösten lukitsemista.", "cycle.api-productization-cycle.station.api-platform-architecture.description": "Valitse ja validoi API-tuotteen tarvitsema API-alusta, arkkitehtuuri, hallintamalli ja operatiiviset rajoitteet.", @@ -61,7 +47,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Seuraa APIen tilaa, käyttöönottoa, hyödyntäjien tuloksia, luotettavuutta ja parannusmahdollisuuksia julkaisun jälkeen.", "cycle.automation-cycle.title": "Automaatiosykli", "cycle.automation-cycle.description": "Sykli automaatioratkaisujen valintaan, suunnitteluun, toimittamiseen, käyttöönottoon ja parantamiseen ihmisten, sääntöjen, työnkulkujen, agenttien, integraatioiden, käyttöliittymäautomaation ja operoinnin yli.", - "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", + "cycle.automation-cycle.purpose": "Ohjaa tiimejä ulkoisen asiakkaan ja kyvykkyyden tuloksista validoituun, hallittuun ja operoitavaan automaatioratkaisuun.", "cycle.audience.automation-owners": "Automaation omistajat", "cycle.audience.process-owners": "Prosessinomistajat", "cycle.audience.automation-teams": "Automaatiotiimit", @@ -71,33 +57,33 @@ "cycle.station.automation-readiness-review": "Automaation valmiuskatselmointi", "cycle.station.automation-enablement": "Automaation kayttoonotto ja kayttoonoton tuki", "cycle.station.automation-monitoring-improvement": "Automaation seuranta ja parantaminen", - "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", - "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", - "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", + "cycle.automation-cycle.station.api-product-strategy.description": "Aloita merkityksellisimmästä ulkoisesta asiakkaasta. Hyödynnä polku- ja kyvykkyysarvon näyttöä sen validoimiseksi, pitäisikö automaation hypoteesia edistää.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Selvenn? prosessi-, kokemus-, toimialue-, palvelu- ja ei-toiminnalliset vaatimukset, jotka myöhemmän työnkulun ja arkkitehtuurin on täytettävä.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Valitse automaation toteutustapa vaikutusten, sijainnin, kapasiteetin ja aiempien vaatimusten perusteella sekä kirjaa perustelut ja jäljellä olevat riskit.", + "cycle.automation-cycle.station.api-design.description": "Suunnittele sisäinen työnkulku, jolla valitut asiakas- ja kyvykkyystulokset tuotetaan, mukaan lukien työnjako, kontrollit, poikkeukset, palautuminen, näyttö ja seuranta.", + "cycle.automation-cycle.station.api-delivery.description": "Rakenna, konfiguroi, testaa, versioi ja julkaise valittu automaatiopolku sekä valmistele sen toimintamalli, mukaan lukien omistajuus, ympäristöt, ajokirjat, seuranta, varamenettely, palautus, tuki ja tunnetut riskit.", "cycle.automation-cycle.station.api-audit.description": "Käytä valmiustarkistuslistaa näytön arviointiin ja julkaisupäätöksen kirjaamiseen: valmis, ehdollisesti valmis, korjaus tarvitaan tai ei hyväksytty.", "cycle.automation-cycle.station.api-publishing.description": "Aktivoi ja ota automaatio turvallisesti käyttöön viestinnän, koulutuksen, toimintaohjeiden, tukipolkujen, käyttöönoton seurannan, palautekanavien, vaiheistetun rollout-suunnitelman sekä pysäytys- ja palautusehtojen avulla.", - "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", - "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", + "cycle.automation-cycle.station.monitoring-and-improving.description": "Seuraa automaation toteutuneita tuloksia, ajojen onnistumista ja epäonnistumista, poikkeuksia, uudelleenyrityksiä, puuttumisia, läpimenoaikaa, odotusaikaa, kustannuksia, virheitä, epävarmoja toimia, käyttöönottoa, luottamusta, toteutunutta hyötyä sekä sitä, mitkä hypoteesin oletukset vahvistuivat tai kumoutuivat.", + "cycle.station.process-user-automation-requirements": "Prosessi- ja kokemusvaatimukset", + "cycle.station.automation-architecture-platform-decision": "Automaatioarkkitehtuurin ja alustan päätös", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Aloita asiakaspolusta, kyvykkyyden arvosta ja elinkelpoisuutta koskevasta näytöstä ja validoi sitten, pitäisikö ehdotettua uudelleenkäytettävää integraatiokyvykkyyttä edistää.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Sovi tarjoajan ja hyödyntäjän sitoumukset pääsyst?, validoinnista, palvelusta, vikatilanteiden käsittelystä, palautumisesta, yhteensopivuudesta ja elinkaaresta.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Valitse integraatioarkkitehtuuri, toteutustyyli ja alustakyvykkyydet reunaehtojen ja governancen perusteella.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Suunnittele integraatioratkaisu, sopimukset, skeemat, tietorakenteet, mäppäykset sekä vuorovaikutus- tai toimitusmallit valitulle tyylille.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Rakenna, testaa, deployaa ja operoi integraatiokyvykkyys valitun toteutustyylin ja validoidun sopimuksen mukaisesti.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Varmista integraation valmius, governance, laatu, security, compliance ja operatiivinen näyttö ennen julkaisua.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Julkaise integraatiokyvykkyys, jotta tiimit voivat löytää sen, arvioida sen, pyytää pääsyä, onboardata, käyttää uudelleen ja saada tukea.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Seuraa integraation luotettavuutta, uudelleenkäyttöä, incidentejä, suorituskykyä, kuluttajatuloksia ja parannustarpeita.", - "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", + "cycle.station.consumer-producer-service-requirements": "Hyödyntäjän ja tuottajan sitoumukset", "cycle.station.capability-architecture-platform-decisions": "Kyvykkyyden arkkitehtuuri- ja alustapäätökset", "cycle.station.capability-solution-interaction-design": "Kyvykkyysratkaisun ja vuorovaikutuksen suunnittelu", "cycle.station.capability-delivery-operations": "Kyvykkyyden toimitus ja operointi", "cycle.station.capability-readiness-assurance": "Kyvykkyyden valmiuden varmistus", "cycle.station.capability-publishing-enablement": "Kyvykkyyden julkaisu ja enablement", "cycle.station.capability-monitoring-improvement": "Kyvykkyyden seuranta ja parantaminen", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Aloita asiakaspolusta, kyvykkyyden arvosta ja elinkelpoisuutta koskevasta näytöstä ja validoi sitten, pitäisikö ehdotettua uudelleenkäytettävää digitaalista kyvykkyyttä edistää.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Sovi omistajan, tuottajan ja hyödyntäjän keskinäiset sitoumukset pääsyst?, palvelusta, tuesta, muutoksista ja elinkaaresta.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Kyvykkyyden arkkitehtuuri- ja alustapäätökset: Ohjaa uudelleenkäytettävän kyvykkyyden määrittelyä hypoteesista ja kuluttaja-/tuottajavaatimuksista arkkitehtuuriin, ratkaisusuunnitteluun, toimitukseen, valmiuteen, julkaisuun ja jatkuvaan parantamiseen.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Kyvykkyysratkaisun ja vuorovaikutuksen suunnittelu: Ohjaa uudelleenkäytettävän kyvykkyyden määrittelyä hypoteesista ja kuluttaja-/tuottajavaatimuksista arkkitehtuuriin, ratkaisusuunnitteluun, toimitukseen, valmiuteen, julkaisuun ja jatkuvaan parantamiseen.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Kyvykkyyden toimitus ja operointi: Ohjaa uudelleenkäytettävän kyvykkyyden määrittelyä hypoteesista ja kuluttaja-/tuottajavaatimuksista arkkitehtuuriin, ratkaisusuunnitteluun, toimitukseen, valmiuteen, julkaisuun ja jatkuvaan parantamiseen.", diff --git a/src/data/method/fi/labels.resources.json b/src/data/method/fi/labels.resources.json index 05be628..5c446a9 100644 --- a/src/data/method/fi/labels.resources.json +++ b/src/data/method/fi/labels.resources.json @@ -67,7 +67,7 @@ "resource.contract-first-design.title": "Sopimus ensin -integraatiosuunnittelu", "resource.contract-first-design.description": "Guidance for validating integration contracts before delivery, including OpenAPI, AsyncAPI, event schemas, message schemas, file schemas, data contracts, and interface specifications.", "resource.contract-first-design.outcomes": "Yhteinen ymmärrys resurssin Sopimuslähtöinen suunnittelu tarkoituksesta ja käytöstä", - "resource.contract-first-design.steps": "Apply contract-first or design-first approaches to validate integration contracts before implementation.", + "resource.contract-first-design.steps": "Käytä contract-first- tai design-first-lähestymistapoja integraatiosopimusten validoimiseen ennen toteutusta.", "resource.contract-first-design.tips": "Mukauta resurssi omaan toimintaympäristöösi.", "resource.cross-functional-collaboration-best-practices.title": "Toimialarajat ylittävän yhteistyön parhaat käytännöt", "resource.cross-functional-collaboration-best-practices.description": "Käytännöt, joilla helpotetaan viestintää ja yhdenmukaistamista liiketoiminta- ja tekniikkatiimien välillä API-rajapintoja suunniteltaessa tai toimitettaessa.", @@ -150,20 +150,20 @@ "resource.api-value-proposition-canvas.steps": "Listaa käyttäjäpolun tehtävät.", "resource.api-value-proposition-canvas.tips": "Hyödynnä Asiakaspolkukanvasin tietoja", "resource.business-impact-canvas.title": "Liiketoimintavaikutuskanvas", - "resource.business-impact-canvas.description": "Assess expected benefits, operational, customer, employee, financial, compliance, strategic, risk, and not-proceeding impacts that should shape prioritization and decisions.", - "resource.business-impact-canvas.outcomes": "Documented business impact assessment", - "resource.business-impact-canvas.steps": "Identify expected business, customer, employee, quality, speed, risk, compliance, and strategic benefits.", - "resource.business-impact-canvas.tips": "Use this for value and consequence evidence, not only risk and resilience analysis.", + "resource.business-impact-canvas.description": "Arvioi odotetut hyödyt sekä operatiiviset, asiakas-, työntekijä-, taloudelliset, vaatimustenmukaisuus-, strategiset, riski- ja etenemättä jättämisen vaikutukset, joiden tulisi ohjata priorisointia ja päätöksiä.", + "resource.business-impact-canvas.outcomes": "Dokumentoitu liiketoimintavaikutusten arviointi", + "resource.business-impact-canvas.steps": "Tunnista odotetut liiketoiminta-, asiakas-, työntekijä-, laatu-, nopeus-, riski-, vaatimustenmukaisuus- ja strategiset hyödyt.", + "resource.business-impact-canvas.tips": "Käytä tätä arvon ja seurausten näyttöön, ei vain riskien ja resilienssin analysointiin.", "resource.capacity-canvas.title": "Kapasiteettikanvas", - "resource.capacity-canvas.description": "Quantify demand, load, timing, availability, and scaling needs for capabilities, automations, integrations, or services.", + "resource.capacity-canvas.description": "Mittaa kyvykkyyksien, automaatioiden, integraatioiden tai palvelujen kysyntä, kuorma, ajoitus, saatavuus ja skaalaustarpeet.", "resource.capacity-canvas.outcomes": "Liiketoiminnan odotettuun kysyntään sovitetut kapasiteettivaatimukset", - "resource.capacity-canvas.steps": "Current Business Volumes: Quantify current business volumes and transaction rates.", - "resource.capacity-canvas.tips": "Use requirements canvases to capture what users need; use this canvas to quantify demand and inform scaling decisions.", - "resource.customer-journey-canvas.title": "Customer Journey Canvas", - "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", - "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", - "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", + "resource.capacity-canvas.steps": "Nykyiset liiketoimintavolyymit: mittaa nykyiset liiketoimintavolyymit ja tapahtumamäärät.", + "resource.capacity-canvas.tips": "Käytä vaatimuskanvaksia käyttäjien tarpeiden kuvaamiseen; käytä tätä kanvasta kysynnän mittaamiseen ja skaalauspäätösten tukemiseen.", + "resource.customer-journey-canvas.title": "Asiakaspolkukanvas", + "resource.customer-journey-canvas.description": "Millaisen polun merkityksellisin ulkoinen asiakas kokee, ja mitä pitäisi parantaa?", + "resource.customer-journey-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.customer-journey-canvas.steps": "Aloita merkityksellisimmästä ulkoisesta asiakkaasta. Kuvaa hänen todellinen polkunsa ennen kuin etenet sisäänpäin kyvykkyyksiin, sisäisiin prosesseihin tai toteutusvalintoihin.", + "resource.customer-journey-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", "resource.event-canvas.title": "Tapahtumakanvas", "resource.event-canvas.description": "Suunnittele tapahtumapohjaiset rajapinnat ja integraatiot määrittelemällä tapahtumat, laukaisimet, skeemat, tuottajat, hyödyntäjät ja käsittelylogiikka.", "resource.event-canvas.outcomes": "Määritelty tapahtumapohjainen vuorovaikutusmalli", @@ -255,8 +255,8 @@ "resource.competitor-analysis-template.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.", "resource.contract-first-design.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Sopimuslähtöinen suunnittelu", "resource.contract-first-design.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen", - "resource.contract-first-design.steps.1": "Define interface contracts, schemas, responsibilities, usage rules, examples, and lifecycle expectations.", - "resource.contract-first-design.steps.2": "Use machine-readable formats such as OpenAPI, AsyncAPI, event schemas, message schemas, file schemas, data contracts, or interface specifications where possible.", + "resource.contract-first-design.steps.1": "Määrittele rajapintasopimukset, skeemat, vastuut, käyttösäännöt, esimerkit ja elinkaariodotukset.", + "resource.contract-first-design.steps.2": "Käytä mahdollisuuksien mukaan koneluettavia muotoja, kuten OpenAPIa, AsyncAPIa, tapahtumaskeemoja, viestiskeemoja, tiedostoskeemoja, datasopimuksia tai rajapintamäärityksiä.", "resource.contract-first-design.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.", "resource.cross-functional-collaboration-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Toimialarajat ylittävän yhteistyön parhaat käytännöt", "resource.cross-functional-collaboration-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen", @@ -335,33 +335,33 @@ "resource.api-value-proposition-canvas.steps.3": "Ominaisuuksien kartoittaminen API-tuotteisiin", "resource.api-value-proposition-canvas.tips.1": "Korosta ominaisuuksia, jotka vähentävät kipupisteitä tai vahvistavat tavoiteltuja hyötyjä.", "resource.api-value-proposition-canvas.tips.2": "Validoi ominaisuudet API-hyödyntäjien kanssa yhdenmukaistamisen varmistamiseksi.", - "resource.business-impact-canvas.outcomes.1": "Expected value, affected groups, financial and strategic consequences, risks, and mitigations clarified", + "resource.business-impact-canvas.outcomes.1": "Odotettu arvo, vaikutuksen kohteena olevat ryhmät, taloudelliset ja strategiset seuraukset, riskit ja lievennykset on selvennetty", "resource.business-impact-canvas.outcomes.2": "Näyttö opportunity-, arkkitehtuuri-, rollout-, valmius- sekä jatka-tai-pysäytä-päätöksiin", - "resource.business-impact-canvas.steps.1": "Assess operational efficiency, customer and employee impact, financial impact, compliance impact, strategic impact, and impact of not proceeding.", + "resource.business-impact-canvas.steps.1": "Arvioi operatiivinen tehokkuus, asiakas- ja työntekijävaikutukset, taloudelliset vaikutukset, vaatimustenmukaisuusvaikutukset, strategiset vaikutukset ja etenemättä jättämisen vaikutukset.", "resource.business-impact-canvas.steps.2": "Tunnista riskit, kriittisyys, hallintatoimet, jäännösriskit ja päätösten seuraukset.", "resource.business-impact-canvas.steps.3": "Käytä vaikutusnäyttöä priorisoinnin, arkkitehtuurin, rollout-suunnitelman, valmiuden ja jatka-tai-pysäytä-päätösten ohjaamiseen.", "resource.business-impact-canvas.steps.4": "Tietoriskit: Tunnista tietojen tarkkuuteen tai saatavuuteen liittyvät riskit.", "resource.business-impact-canvas.steps.5": "Tietoriskien lieventämistavat: Suunnittele strategioita tietoriskien torjumiseksi.", - "resource.business-impact-canvas.tips.1": "Include business stakeholders, users or employees, operations, compliance, and technical stakeholders.", - "resource.business-impact-canvas.tips.2": "Record the impact of not proceeding as well as expected benefits.", + "resource.business-impact-canvas.tips.1": "Ota mukaan liiketoiminnan sidosryhmät, käyttäjät tai työntekijät, operatiiviset toimijat, vaatimustenmukaisuus sekä tekniset sidosryhmät.", + "resource.business-impact-canvas.tips.2": "Kirjaa etenemättä jättämisen vaikutus sekä odotetut hyödyt.", "resource.capacity-canvas.outcomes.1": "Dokumentoidut oletukset kuormitushuipuista, saatavuudesta ja kasvusta", "resource.capacity-canvas.outcomes.2": "Määritellyt skaalaus-, välimuisti- ja kutsurajoitusratkaisut", - "resource.capacity-canvas.steps.1": "Future Consumption Trends: Estimate future demand and growth assumptions.", - "resource.capacity-canvas.steps.2": "Peak Load and Availability Requirements: Quantify peak load and availability needs.", - "resource.capacity-canvas.steps.3": "Caching, rate limiting, and scaling approaches: Record architecture follow-up options where capacity requires them.", + "resource.capacity-canvas.steps.1": "Tulevat kulutustrendit: arvioi tuleva kysyntä ja kasvuoletukset.", + "resource.capacity-canvas.steps.2": "Huippukuorman ja saatavuuden vaatimukset: mittaa huippukuorma ja saatavuustarpeet.", + "resource.capacity-canvas.steps.3": "Välimuisti, nopeusrajoitukset ja skaalausmallit: kirjaa arkkitehtuurin jatkovaihtoehdot, kun kapasiteetti niitä edellyttää.", "resource.capacity-canvas.steps.4": "Ehdotetaan skaalausstrategioita", "resource.capacity-canvas.tips.1": "Käytä mitattua tietoa aina kun sitä on saatavilla ja kirjaa oletukset näkyviin.", "resource.capacity-canvas.tips.2": "Päivitä kanvas pilotin tai kysynnän olennaisten muutosten jälkeen.", - "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.customer-journey-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.customer-journey-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.customer-journey-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.customer-journey-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", "resource.customer-journey-canvas.steps.3": "Kartoita matkan vaiheet ja syötteet/lähtötiedot", "resource.customer-journey-canvas.steps.4": "Tunnista asiakkaan kipupisteet", "resource.customer-journey-canvas.steps.5": "Yhteenveto asiakkaan saamista eduista", "resource.customer-journey-canvas.steps.6": "Määritellään tarvittavat syötteet ja tuotokset", "resource.customer-journey-canvas.steps.7": "Määrittele API-vuorovaikutukset kullekin vaiheelle", - "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.customer-journey-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", "resource.event-canvas.outcomes.1": "Selkeytetyt tapahtumat, laukaisimet, skeemat, tuottajat ja hyödyntäjät", "resource.event-canvas.outcomes.2": "Dokumentoidut käsittely-, kuittaus- ja virhetilanneodotukset", "resource.event-canvas.steps.1": "Määritä laukaisimet kullekin tapahtumalle", @@ -519,9 +519,9 @@ "resource.automation-readiness-checklist.outcomes": "Automaation valmiuspäätös", "resource.automation-readiness-checklist.outcomes.1": "Julkaisupäätös kirjattu tilaan valmis, ehdollisesti valmis, korjaus tarvitaan tai ei hyväksytty", "resource.automation-readiness-checklist.outcomes.2": "Näyttö, estävät havainnot, jäännösriskit, ehdot, korjaustoimet, päätöksen omistaja ja päätöspäivä dokumentoitu ennen julkaisua", - "resource.automation-readiness-checklist.steps": "Review completed operating model, workflow design, business rules, controls, access, data handling, exception paths, and evidence.", + "resource.automation-readiness-checklist.steps": "Tarkista valmis toimintamalli, työnkulun suunnittelu, liiketoimintasäännöt, kontrollit, pääsy, datankäsittely, poikkeuspolut ja näyttö.", "resource.automation-readiness-checklist.steps.1": "Tunnista estävät havainnot, hyväksytyt jäännösriskit, puuttuva näyttö ja tarvittavat korjaustoimet.", - "resource.automation-readiness-checklist.steps.2": "Record the release decision, decision owner, decision date, conditions, and follow-up actions.", + "resource.automation-readiness-checklist.steps.2": "Kirjaa julkaisupäätös, päätöksen omistaja, päätöspäivä, ehdot ja jatkotoimet.", "resource.automation-readiness-checklist.steps.3": "Kirjaa avoimet puutteet, päätökset ja hyväksytyt riskit ennen julkaisua.", "resource.automation-readiness-checklist.tips": "Käytä ennen julkaisua ja uudelleen olennaisten työnkulku- tai sääntömuutosten jälkeen.", "resource.automation-readiness-checklist.tips.1": "Tee ihmisen valvonta ja poikkeusten käsittely näkyväksi näytössä.", @@ -542,107 +542,107 @@ "resource.api-testing-best-practices.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.", "resource.apiops-CI-CD-for-apis.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.", "resource.api-audit-checklist.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.", - "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", - "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", - "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", - "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", - "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", - "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", - "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", - "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", - "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", - "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", - "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", - "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", - "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", - "resource.user-operator-experience-requirements.outcomes.1": "Availability, timeliness, permissions, support, recovery, observability, and activation needs captured", - "resource.user-operator-experience-requirements.outcomes.2": "Constraints ready for later architecture, workflow, and capacity decisions", - "resource.user-operator-experience-requirements.steps": "Capture user, operator, approver, and support goals for the target process.", - "resource.user-operator-experience-requirements.steps.1": "Clarify availability, timeliness, volume, data quality, permissions, activation, changes, support, observability, recovery, and continuity expectations.", - "resource.user-operator-experience-requirements.steps.2": "Translate the expectations into constraints for later automation design without choosing the implementation mechanism.", - "resource.user-operator-experience-requirements.tips": "Use this label in the Automation Cycle instead of API consumer wording.", - "resource.user-operator-experience-requirements.tips.1": "Keep the shared underlying requirements canvas intact for other cycles.", - "resource.automation-monitoring-value-metrics.title": "Automation Monitoring and Value Metrics", + "resource.automation-opportunity-canvas.title": "Automaation hypoteesi- ja validointikanvas", + "resource.automation-opportunity-canvas.description": "Muunna olemassa oleva polku-, arvo-, vaikutus-, toimialue- ja kapasiteettinäyttö testattavaksi automaatiopäätökseksi.", + "resource.automation-opportunity-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.automation-opportunity-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.automation-opportunity-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.automation-opportunity-canvas.steps": "Hyödynnä aiempien kanvasten tuotoksia. Kirjaa vain jäljellä oleva hypoteesi, epävarmuudet, validointi ja päätös.", + "resource.automation-opportunity-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.automation-opportunity-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.automation-opportunity-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.automation-opportunity-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.automation-workflow-canvas.title": "Automaation työnkulkukanvas", + "resource.automation-workflow-canvas.description": "Suunnittele sisäinen työnkulku, jolla valitut asiakas- ja kyvykkyystulokset tuotetaan.", + "resource.automation-workflow-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.automation-workflow-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.automation-workflow-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.automation-workflow-canvas.steps": "Hyödynnä asiakaspolun, arvolupauksen, toimialueen ja validoinnin näyttöä. Määrittele sisäinen työ, jaa se ihmisten ja automaation välillä ja lisää vain toteutuksen yksityiskohdat.", + "resource.automation-workflow-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.automation-workflow-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.automation-workflow-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.automation-workflow-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.automation-architecture-decision-canvas.title": "Automaatioarkkitehtuurin päätöskanvas", + "resource.automation-architecture-decision-canvas.description": "Valitse toteutustapa jo kerätyn näytön perusteella.", + "resource.automation-architecture-decision-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.automation-architecture-decision-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.automation-architecture-decision-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.automation-architecture-decision-canvas.steps": "Tuo rajoitteet ja vastuuvalinnat mukaan. Vertaa vain toteuttamiskelpoisia mekanismeja ja kirjaa sitten päätös sekä jäljellä olevat riskit.", + "resource.automation-architecture-decision-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.automation-architecture-decision-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.automation-architecture-decision-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.automation-architecture-decision-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.automation-readiness-operations-canvas.title": "Automaation valmius- ja operointikanvas", + "resource.automation-readiness-operations-canvas.description": "Valmistele vähimmäisnäyttö operoinnista ennen valmiustarkastusta.", + "resource.automation-readiness-operations-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.automation-readiness-operations-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.automation-readiness-operations-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.automation-readiness-operations-canvas.steps": "Hyödynnä suunnittelupäätöksiä. Kirjaa omistajuus, operatiiviset järjestelyt, näyttö, palautuminen ja jäljellä olevat valmiuspuutteet.", + "resource.automation-readiness-operations-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.automation-readiness-operations-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.automation-readiness-operations-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.automation-readiness-operations-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.user-operator-experience-requirements.title": "Käyttäjä- ja operaattorikokemuksen vaatimukset", + "resource.user-operator-experience-requirements.description": "Syklikohtainen näkymä automaation käyttäjien, operaattorien, hyväksyjien ja tukitiimien kokemus-, operatiivisiin ja ei-toiminnallisiin vaatimuksiin.", + "resource.user-operator-experience-requirements.outcomes": "Käyttäjien ja operaattorien odotukset on selvennetty", + "resource.user-operator-experience-requirements.outcomes.1": "Saatavuus-, ajantasaisuus-, käyttöoikeus-, tuki-, palautumis-, havainnoitavuus- ja aktivointitarpeet on kuvattu", + "resource.user-operator-experience-requirements.outcomes.2": "Rajoitteet ovat valmiina myöhempiä arkkitehtuuri-, työnkulku- ja kapasiteettipäätöksiä varten", + "resource.user-operator-experience-requirements.steps": "Kuvaa kohdeprosessin käyttäjä-, operaattori-, hyväksyjä- ja tukitavoitteet.", + "resource.user-operator-experience-requirements.steps.1": "Selvenn? saatavuuteen, ajantasaisuuteen, volyymiin, datan laatuun, käyttöoikeuksiin, aktivointiin, muutoksiin, tukeen, havainnoitavuuteen, palautumiseen ja jatkuvuuteen liittyvät odotukset.", + "resource.user-operator-experience-requirements.steps.2": "Muunna odotukset myöhemmän automaatiosuunnittelun rajoitteiksi valitsematta toteutusmekanismia.", + "resource.user-operator-experience-requirements.tips": "Käytä tätä nimeä Automaatiosyklissä API-hyödyntäjäsanaston sijaan.", + "resource.user-operator-experience-requirements.tips.1": "Pidä jaettu taustalla oleva vaatimuskanvas ennallaan muita syklejä varten.", + "resource.automation-monitoring-value-metrics.title": "Automaation seuranta ja arvomittarit", "resource.automation-monitoring-value-metrics.description": "Ohje tulosten, operatiivisen suorituskyvyn, käyttäytymisen, riskien, palautumisen, toteutuneen arvon, hypoteeseista oppimisen ja elinkaaripäätösten mittaamiseen rolloutin jälkeen.", - "resource.automation-monitoring-value-metrics.outcomes": "Automation monitoring, value, and learning evidence", - "resource.automation-monitoring-value-metrics.outcomes.1": "Actual outcomes, run success, failure, exception, retry, intervention, processing time, waiting time, correction, incident, adoption, and benefit signals reviewed", - "resource.automation-monitoring-value-metrics.outcomes.2": "Automation Hypothesis assumptions reviewed and improvement, expansion, redesign, or retirement decisions prioritized", - "resource.automation-monitoring-value-metrics.steps": "Outcomes and value: compare expected process, user, and business outcomes with actual evidence.", - "resource.automation-monitoring-value-metrics.steps.1": "Operational performance: review successful runs, failures, partial completions, exceptions, retries, timeouts, interventions, processing time, waiting time, and cost.", - "resource.automation-monitoring-value-metrics.steps.2": "User, risk, and recovery signals: review errors, corrections, unsafe actions, bypassing, mistrust, support needs, fallback events, and recovery failures.", - "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", + "resource.automation-monitoring-value-metrics.outcomes": "Automaation seuranta-, arvo- ja oppimisnäyttö", + "resource.automation-monitoring-value-metrics.outcomes.1": "Toteutuneet tulokset, ajojen onnistumiset, epäonnistumiset, poikkeukset, uudelleenyritykset, puuttumiset, käsittelyaika, odotusaika, korjaukset, häiriöt, käyttöönotto ja hyötysignaalit on arvioitu", + "resource.automation-monitoring-value-metrics.outcomes.2": "Automaation hypoteesin oletukset on arvioitu ja parannus-, laajennus-, uudelleensuunnittelu- tai käytöstäpoistopäätökset priorisoitu", + "resource.automation-monitoring-value-metrics.steps": "Tulokset ja arvo: vertaa odotettuja prosessi-, käyttäjä- ja liiketoimintatuloksia toteutuneeseen näyttöön.", + "resource.automation-monitoring-value-metrics.steps.1": "Operatiivinen suorituskyky: arvioi onnistuneet ajot, epäonnistumiset, osittaiset valmistumiset, poikkeukset, uudelleenyritykset, aikakatkaisut, puuttumiset, käsittelyaika, odotusaika ja kustannukset.", + "resource.automation-monitoring-value-metrics.steps.2": "Käyttäjä-, riski- ja palautumissignaalit: arvioi virheet, korjaukset, epävarmat toimet, ohitukset, epäluottamus, tukitarpeet, varamenettelytapahtumat ja palautumisen epäonnistumiset.", + "resource.automation-monitoring-value-metrics.steps.3": "Oppiminen ja elinkaaripäätös: päätä, mitkä hypoteesin oletukset vahvistuivat tai kumoutuivat ja parannetaanko, laajennetaanko, rajoitetaanko, suunnitellaanko uudelleen, keskeytetäänkö, poistetaanko käytöstä vai lisätäänkö backlog-tehtäviä.", "resource.automation-monitoring-value-metrics.tips": "Seuranta muuntaa operatiivisen, käyttäjä-, riski- ja arvonäytön elinkaaripäätöksiksi ja parannusbacklogiksi.", - "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", - "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", - "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", - "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", - "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", - "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", - "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", - "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", - "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", - "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.automation-monitoring-value-metrics.tips.1": "Sisällytä signaalit, jotka osoittavat käyttöönottoa, luottamusta, ihmisen valvonnan tarpeita, palautumistarpeita ja toteutunutta arvoa.", + "resource.integration-capability-hypothesis-canvas.title": "Integraatiokyvykkyyden validointikanvas", + "resource.integration-capability-hypothesis-canvas.description": "Validoi, pitäisikö ehdotettua uudelleenkäytettävää integraatiokyvykkyyttä edistää.", + "resource.integration-capability-hypothesis-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.integration-capability-hypothesis-canvas.steps": "Hyödynnä polku-, arvo-, toimialue-, liiketoimintamalli-, vaikutus- ja kapasiteettinäyttöä sen uudelleenkuvaamisen sijaan.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.integration-capability-hypothesis-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.integration-consumer-provider-requirements-canvas.title": "Integraation hyödyntäjän ja tarjoajan sitoumuskanvas", + "resource.integration-consumer-provider-requirements-canvas.description": "Sovi vastuista, joita tarvitaan uudelleenkäytettävän integraatiokyvykkyyden hyödyntämiseen ja tarjoamiseen.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.integration-consumer-provider-requirements-canvas.steps": "Tuo esiin hyödyntäjät, käyttötapaukset, palvelutarpeet ja rajoitteet. Kirjaa sitoumukset sen sijaan, että vaatimukset löydettäisiin uudelleen.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.integration-architecture-decision-canvas.title": "Integraatioarkkitehtuurin päätöskanvas", + "resource.integration-architecture-decision-canvas.description": "Valitse integraatiotyyli ja alusta jo kerätyn näytön perusteella.", + "resource.integration-architecture-decision-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.integration-architecture-decision-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.integration-architecture-decision-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.integration-architecture-decision-canvas.steps": "Tuo mukaan hyödyntäjän sitoumukset, vaikutus, sijainti ja kapasiteetti. Vertaa vain toteuttamiskelpoisia tyylejä ja kirjaa päätös.", + "resource.integration-architecture-decision-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.integration-architecture-decision-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.integration-architecture-decision-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.integration-architecture-decision-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.integration-readiness-operations-canvas.title": "Integraation valmius- ja operointikanvas", + "resource.integration-readiness-operations-canvas.description": "Valmistele integraation valmiustarkastusta varten tarvittava vähimmäisnäyttö operoinnista.", + "resource.integration-readiness-operations-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.integration-readiness-operations-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.integration-readiness-operations-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.integration-readiness-operations-canvas.steps": "Hyödynnä sopimuksia ja suunnittelupäätöksiä. Kirjaa omistajuus, operointi, näyttö, palautuminen ja jäljellä olevat valmiuspuutteet.", + "resource.integration-readiness-operations-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.integration-readiness-operations-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.integration-readiness-operations-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.integration-readiness-operations-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", "resource.integration-consumer-onboarding-guide.title": "Integraation kuluttaja-onboardingin opas", "resource.integration-consumer-onboarding-guide.description": "Integraation kuluttaja-onboardingin opas tukee uudelleenkäytettävän integraatiokyvykkyyden suunnittelua, päätöksentekoa, toimitusta, julkaisua tai parantamista.", "resource.integration-consumer-onboarding-guide.outcomes": "Dokumentoitu integraation työpohja", @@ -813,66 +813,66 @@ "resource.integration-lifecycle-management-guide.steps.2": "Hyödynnä tuloksia suunnittelussa, toimituksessa, valmiusarvioinnissa, julkaisussa tai parantamisessa.", "resource.integration-lifecycle-management-guide.tips": "Sovita tämä resurssi valittuun integraatiotyyliin.", "resource.integration-lifecycle-management-guide.tips.1": "Ota mukaan tuottajat, kuluttajat, alusta, operointi, security, compliance ja business.", - "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", - "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", - "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", - "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", - "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", - "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", - "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", - "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", - "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", - "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", - "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", - "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", - "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", - "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", - "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", - "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", - "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-solution-design-canvas.title": "Integraatioratkaisun suunnittelukanvas", + "resource.integration-solution-design-canvas.description": "Tarkenna valittu arkkitehtuuri toteutuskelpoiseksi integraatiosuunnitelmaksi.", + "resource.integration-solution-design-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.integration-solution-design-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.integration-solution-design-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.integration-solution-design-canvas.steps": "Hyödynnä valittua tyyliä, toimialuekäsitteitä, vuorovaikutustarpeita ja sitoumuksia. Lisää vain toteutuskohtainen suunnittelu.", + "resource.integration-solution-design-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.integration-solution-design-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.integration-solution-design-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.integration-solution-design-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.capability-hypothesis-canvas.title": "Kyvykkyyden validointikanvas", + "resource.capability-hypothesis-canvas.description": "Validoi, pitäisikö ehdotettua uudelleenkäytettävää digitaalista kyvykkyyttä edistää.", + "resource.capability-hypothesis-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.capability-hypothesis-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.capability-hypothesis-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.capability-hypothesis-canvas.steps": "Hyödynnä polun, arvolupauksen, liiketoimintamallin, vaikutusten, toimialueen ja kapasiteetin tuotoksia niiden toistamisen sijaan.", + "resource.capability-hypothesis-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.capability-hypothesis-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.capability-hypothesis-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.capability-hypothesis-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.capability-consumer-producer-requirements-canvas.title": "Kyvykkyyden hyödyntäjän ja tuottajan sitoumuskanvas", + "resource.capability-consumer-producer-requirements-canvas.description": "Sovi keskinäisistä sitoumuksista uudelleenkäytettävän kyvykkyyden tarjoamiseksi ja hyödyntämiseksi.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.capability-consumer-producer-requirements-canvas.steps": "Hyödynnä aiempien kanvasten hyödyntäjiä, arvoa, kanavia, palvelutarpeita ja omistajuutta. Kuvaa vain sovitut sitoumukset ja puutteet.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.capability-architecture-decision-canvas.title": "Kyvykkyysarkkitehtuurin päätöskanvas", + "resource.capability-architecture-decision-canvas.description": "Valitse jo kerätyn näytön perusteella, miten kyvykkyys toimitetaan.", + "resource.capability-architecture-decision-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.capability-architecture-decision-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.capability-architecture-decision-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.capability-architecture-decision-canvas.steps": "Tuo mukaan arvo, sitoumukset, vaikutus, sijainti, kapasiteetti ja toimialuepäätökset. Vertaa vain toteuttamiskelpoisia toteutustyylejä.", + "resource.capability-architecture-decision-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.capability-architecture-decision-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.capability-architecture-decision-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.capability-architecture-decision-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.capability-solution-design-canvas.title": "Kyvykkyysratkaisun suunnittelukanvas", + "resource.capability-solution-design-canvas.description": "Tarkenna valittu toteutustyyli selkeäksi hyödyntäjälle näkyväksi kyvykkyyssuunnitelmaksi.", + "resource.capability-solution-design-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.capability-solution-design-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.capability-solution-design-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.capability-solution-design-canvas.steps": "Hyödynnä arvo-, toimialue-, vuorovaikutus-, sitoumus- ja arkkitehtuurituotoksia. Lisää vain ratkaisukohtainen suunnittelu.", + "resource.capability-solution-design-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.capability-solution-design-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.capability-solution-design-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.capability-solution-design-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", + "resource.capability-readiness-operations-canvas.title": "Kyvykkyyden valmius- ja operointikanvas", + "resource.capability-readiness-operations-canvas.description": "Valmistele kyvykkyyden valmiustarkastusta varten tarvittava vähimmäisnäyttö operoinnista.", + "resource.capability-readiness-operations-canvas.outcomes": "Kohdennettu päätös- tai suunnitteluartefakti, joka hyödyntää aiempaa näyttöä", + "resource.capability-readiness-operations-canvas.outcomes.1": "Aiempiin kanvastuotoksiin viitataan niiden toistamisen sijaan", + "resource.capability-readiness-operations-canvas.outcomes.2": "Seuraava päätös, suunnitteluvaihe tai valmiuspuute on selkeä", + "resource.capability-readiness-operations-canvas.steps": "Hyödynnä liiketoimintamallia, sitoumuksia ja ratkaisusuunnittelua. Kirjaa vain operatiivinen omistajuus, näyttö, jatkuvuus ja valmiuspuutteet.", + "resource.capability-readiness-operations-canvas.steps.1": "Täytä vain ne osiot, jotka lisäävät uuden päätöksen tai tarkennuksen.", + "resource.capability-readiness-operations-canvas.steps.2": "Vie syntyneet päätökset eteenpäin seuraavalle asemalle.", + "resource.capability-readiness-operations-canvas.tips": "Linkitä aiempiin kanvaksiin sen sijaan, että kopioisit niiden sisältää.", + "resource.capability-readiness-operations-canvas.tips.1": "Käytä tukevia kanvaksia vain silloin, kun tarvittavaa näyttöä ei vielä ole.", "resource.capability-consumer-onboarding-guide.title": "Kyvykkyyden kuluttaja-onboardingin opas", "resource.capability-consumer-onboarding-guide.description": "Kyvykkyyden kuluttaja-onboardingin opas tukee kyseistä kyvykkyysvaihetta konkreettisilla päätöksillä, näytöllä, vastuilla, riskeillä ja seuraavilla askeleilla.", "resource.capability-consumer-onboarding-guide.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", diff --git a/src/data/method/fi/labels.stations.json b/src/data/method/fi/labels.stations.json index c52b5a4..708d311 100644 --- a/src/data/method/fi/labels.stations.json +++ b/src/data/method/fi/labels.stations.json @@ -38,20 +38,20 @@ "station.api-audit.title": "Laadun ja valmiuden varmistus", "station.api-audit.description": "Arvioi julkaisuvalmius suunnittelun, testauksen, operoinnin, oikeuksien, valvonnan, tuen, varamenettelyn, palautuksen, riskien ja omistajuuden näytön perusteella ennen tuotantokäyttöä.", "station.api-audit.why_it_matters": "Muodollinen valmiuspäätös estää automaatioratkaisujen julkaisun ilman selkeää näyttöä, hyväksyttyjä riskejä, korjaavia toimia sekä liiketoiminnan ja operoinnin omistajuutta.", - "station.api-audit.apply_in_work": "", + "station.api-audit.apply_in_work": "Käytä valmiusnäyttöä selkeän go-, ehdollinen go- tai no-go-päätöksen tekemiseen ennen tuotantokäyttöä.", "station.api-audit.outcomes": "Muodollinen valmiuspäätös", "station.api-audit.how_it_works": "Tarkista valmis suunnittelu, testinäyttö, toimintamalli, käyttöoikeudet, tunnistetiedot, valvonta, tuki, varamenettely ja palautusjärjestelyt.", "station.api-publishing.title": "Julkaisu ja käyttöönoton mahdollistaminen", "station.api-publishing.description": "Mahdollista julkaistujen ratkaisujen turvallinen käyttöönotto käyttäjille, operoijille, vaikutuksen alaisille tiimeille, käyttäville järjestelmille, palvelukuluttajille ja tukitiimeille.", "station.api-publishing.why_it_matters": "Automaatioratkaisut tuottavat arvoa käyttöönoton jälkeen vasta, kun vaikutuksen alaiset ihmiset ja käyttävät järjestelmät ymmärtävät, mikä muuttuu, miten pääsy ja operointi toimivat, mistä saa tukea ja milloin käyttöönotto pysäytetään, laajennetaan tai palautetaan.", - "station.api-publishing.apply_in_work": "", + "station.api-publishing.apply_in_work": "Suunnittele rollout, käyttöönoton tuki, palaute ja palautus, jotta julkaistut ratkaisut voidaan ottaa käyttöön turvallisesti.", "station.api-publishing.outcomes": "Turvallinen rollout- ja enablement-suunnitelma", "station.api-publishing.how_it_works": "Vaikutuksen alaiset ihmiset ja muuttuva työ: Kuka käyttää, operoi, tukee, hyväksyy, kuluttaa tai on julkaisun vaikutuksen alainen, ja mitkä vastuut, päätökset, luovutukset tai työtavat muuttuvat?", "station.monitoring-and-improving.title": "Seuranta ja parantaminen", - "station.monitoring-and-improving.description": "Monitor actual outcomes, operational performance, user behavior, risk, recovery, realized value, and improvement opportunities after release.", + "station.monitoring-and-improving.description": "Seuraa julkaisun jälkeen toteutuneita tuloksia, operatiivista suorituskykyä, käyttäjien käyttäytymistä, riskejä, palautumista, toteutunutta arvoa ja parannusmahdollisuuksia.", "station.monitoring-and-improving.why_it_matters": "Julkaistut ratkaisut tarvitsevat näyttöä siitä, toteutuvatko odotetut tulokset, missä tarvitaan vielä manuaalista puuttumista tai palautumista ja mikä elinkaaripäätös tehdään seuraavaksi.", - "station.monitoring-and-improving.apply_in_work": "", - "station.monitoring-and-improving.outcomes": "Measured outcome, performance, risk, recovery, and value evidence", + "station.monitoring-and-improving.apply_in_work": "Käytä operatiivista, käyttäjä-, riski- ja arvonäyttöä päättääksesi, mitä parannetaan, laajennetaan, rajoitetaan, keskeytetään tai poistetaan käytöstä.", + "station.monitoring-and-improving.outcomes": "Mitattu tulos-, suorituskyky-, riski-, palautumis- ja arvonäyttö", "station.monitoring-and-improving.how_it_works": "Tulokset ja arvo: Saavutetaanko odotetut prosessi-, käyttäjä- ja liiketoimintatulokset?", "station.user-experience.title": "Käyttäjäkokemus - Suunnittele APIt käyttäjälähtöisesti", "station.user-experience.description": "Varmistetaan, että rajapinnat on suunniteltu loppukäyttäjää ajatellen ja että ne tarjoavat saumattoman ja intuitiivisen käyttökokemuksen.", @@ -236,17 +236,17 @@ "station.api-delivery.how_it_works.5": "Käytä auditoinnin tarkistuslistaa varmistaaksesi, että ratkaisu täyttää toiminnalliset ja ei-toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.", "station.api-audit.outcomes.1": "Näyttö, estävät havainnot, hyväksytyt jäännösriskit ja korjaustoimet arvioitu", "station.api-audit.outcomes.2": "Julkaisupäätös kirjattu tilaan valmis, ehdollisesti valmis, korjaus tarvitaan tai ei hyväksytty", - "station.api-audit.outcomes.3": "Business and operational ownership confirmed before release", + "station.api-audit.outcomes.3": "Liiketoiminta- ja operatiivinen omistajuus vahvistettu ennen julkaisua", "station.api-audit.how_it_works.1": "Varmista, että tunnetut riskit, poikkeukset, vaaralliset toiminnot, ihmisen valvonta, vaatimustenmukaisuusvaatimukset ja ratkaisemattomat oletukset on käsitelty tai hyväksytty nimenomaisesti.", "station.api-audit.how_it_works.2": "Kirjaa estävät löydökset, hyväksytyt jäännösriskit, julkaisuehdot ja vaaditut korjaavat toimet.", "station.api-publishing.outcomes.1": "Vaikutuksen kohteena olevat ihmiset, muuttuneet vastuut, päätökset, siirtymät ja työtavat ymmärretty", "station.api-publishing.outcomes.2": "Aktivointi, pääsy, oikeudet, rollout-lähestymistapa, enablement ja tuki valmisteltu", - "station.api-publishing.outcomes.3": "Feedback, adoption, trust, issue handling, pause, rollback, manual operation, and expansion controls defined", + "station.api-publishing.outcomes.3": "Palaute, käyttöönotto, luottamus, ongelmien käsittely, keskeytys, palautus, manuaalinen operointi ja laajennuksen kontrollit on määritelty", "station.api-publishing.how_it_works.1": "Aktivointi ja käyttöönotto: Miten pääsy, oikeudet, pilotointi, vaiheittainen käyttöönotto, rajatut ryhmät, rinnakkaiskäyttö ja laajentaminen hallitaan?", "station.api-publishing.how_it_works.2": "Käyttöönoton tuki: Mitä viestintää, koulutusta, käyttöohjeita ja tukipolkuja tarvitaan?", - "station.monitoring-and-improving.outcomes.1": "Expected outcomes, run performance, user behavior, risks, support needs, and realized value reviewed", - "station.monitoring-and-improving.outcomes.2": "Hypothesis assumptions and lifecycle options assessed", - "station.monitoring-and-improving.outcomes.3": "Improvement backlog informed by operational, user, risk, and value evidence", + "station.monitoring-and-improving.outcomes.1": "Odotetut tulokset, ajojen suorituskyky, käyttäjien käyttäytyminen, riskit, tukitarpeet ja toteutunut arvo on arvioitu", + "station.monitoring-and-improving.outcomes.2": "Hypoteesin oletukset ja elinkaarivaihtoehdot on arvioitu", + "station.monitoring-and-improving.outcomes.3": "Parannusbacklog perustuu operatiiviseen, käyttäjä-, riski- ja arvonäyttöön", "station.monitoring-and-improving.how_it_works.1": "Operatiivinen suorituskyky: Mitä onnistuneet ajot, epäonnistumiset, osittaiset valmistumiset, poikkeukset, uudelleenyritykset, aikakatkaisut, interventiot, käsittelyaika, odotusaika ja kustannukset osoittavat?", "station.monitoring-and-improving.how_it_works.2": "Käyttäjä-, riski- ja palautumissignaalit: Mitä virheitä, korjauksia, vaarallisia toimia, kiertämistä, epäluottamusta, tukitarpeita, varamenettelyitä tai palautumisvirheitä ilmenee?", "station.user-experience.outcomes.1": "Intuitiiviset ja johdonmukaiset käyttöliittymät", @@ -468,197 +468,5 @@ "station.api-audit.how_it_works.4": "Kirjaa päätöksen omistaja, päätöspäivä ja käytetty näyttö.", "station.api-audit.how_it_works.5": "Varmista, ettei mitään julkaista ilman selkeää liiketoiminnan ja operoinnin omistajuutta.", "station.api-publishing.how_it_works.3": "Palaute ja kontrolli: Miten omaksumista, luottamusta, todellista käyttöä, ongelmia ja odottamatonta käyttäytymistä seurataan, ja mitkä ehdot käynnistävät pysäytyksen, palautuksen tai paluun manuaalityöhön?", - "station.monitoring-and-improving.how_it_works.3": "Oppiminen ja elinkaaripäätös: Mitkä hypoteesin oletukset vahvistuivat tai hylättiin, ja pitäisikö ratkaisua parantaa, laajentaa, rajata, suunnitella uudelleen, pysäyttää tai poistaa käytöstä?", - "station.integration-capability-strategy.title": "Integraatiokyvykkyyden strategia", - "station.integration-capability-strategy.description": "Integraatiokyvykkyyden strategia selkeyttää uudelleenkäytettävän integraatiokyvykkyyden seuraavat päätökset, näytön, vastuut ja riskit. Käytä tukikanvaksia vain silloin, kun tarvittavaa näyttöä ei ole jo olemassa.", - "station.integration-capability-strategy.why_it_matters": "Integraatiotyö pysyy johdonmukaisena, kun kuluttajat, tuottajat, alusta, operointi, security, compliance ja business käyttävät samaa näyttöä ja päätöksiä.", - "station.integration-capability-strategy.apply_in_work": "Käytä asemakohtaisia integraatioresursseja ensisijaisena työpohjana.", - "station.integration-capability-strategy.outcomes": "Dokumentoitu integraatiopäätös tai työpohja", - "station.integration-capability-strategy.outcomes.1": "Keskeiset vastuut, näyttö ja reunaehdot selkeytetty", - "station.integration-capability-strategy.outcomes.2": "Riskit, oletukset ja seuraavat askeleet näkyvissä", - "station.integration-capability-strategy.outcomes.3": "Tulokset valmisteltu seuraavaa asemaa varten", - "station.integration-capability-strategy.how_it_works": "Selkeytä tavoite, rajaus, kuluttajat, tuottajat ja alustakonteksti.", - "station.integration-capability-strategy.how_it_works.1": "Dokumentoi relevantti näyttö, päätökset, riskit ja vastuut.", - "station.integration-capability-strategy.how_it_works.2": "Tarkista riippuvuudet arkkitehtuuriin, suunnitteluun, operointiin, julkaisuun ja seurantaan.", - "station.integration-capability-strategy.how_it_works.3": "Kirjaa avoimet asiat ja seuraavat askeleet.", - "station.integration-consumer-requirements-onboarding.title": "Integraation kuluttajavaatimukset ja onboarding", - "station.integration-consumer-requirements-onboarding.description": "Integraation kuluttajavaatimukset ja onboarding selkeyttää uudelleenkäytettävän integraatiokyvykkyyden seuraavat päätökset, näytön, vastuut ja riskit.", - "station.integration-consumer-requirements-onboarding.why_it_matters": "Integraatiotyö pysyy johdonmukaisena, kun kuluttajat, tuottajat, alusta, operointi, security, compliance ja business käyttävät samaa näyttöä ja päätöksiä.", - "station.integration-consumer-requirements-onboarding.apply_in_work": "Käytä asemakohtaisia integraatioresursseja ensisijaisena työpohjana.", - "station.integration-consumer-requirements-onboarding.outcomes": "Dokumentoitu integraatiopäätös tai työpohja", - "station.integration-consumer-requirements-onboarding.outcomes.1": "Keskeiset vastuut, näyttö ja reunaehdot selkeytetty", - "station.integration-consumer-requirements-onboarding.outcomes.2": "Riskit, oletukset ja seuraavat askeleet näkyvissä", - "station.integration-consumer-requirements-onboarding.outcomes.3": "Tulokset valmisteltu seuraavaa asemaa varten", - "station.integration-consumer-requirements-onboarding.how_it_works": "Selkeytä tavoite, rajaus, kuluttajat, tuottajat ja alustakonteksti.", - "station.integration-consumer-requirements-onboarding.how_it_works.1": "Dokumentoi relevantti näyttö, päätökset, riskit ja vastuut.", - "station.integration-consumer-requirements-onboarding.how_it_works.2": "Tarkista riippuvuudet arkkitehtuuriin, suunnitteluun, operointiin, julkaisuun ja seurantaan.", - "station.integration-consumer-requirements-onboarding.how_it_works.3": "Kirjaa avoimet asiat ja seuraavat askeleet.", - "station.integration-architecture-platform-decisions.title": "Integraation arkkitehtuuri- ja alustapäätökset", - "station.integration-architecture-platform-decisions.description": "Integraation arkkitehtuuri- ja alustapäätökset selkeyttää uudelleenkäytettävän integraatiokyvykkyyden seuraavat päätökset, näytön, vastuut ja riskit.", - "station.integration-architecture-platform-decisions.why_it_matters": "Integraatiotyö pysyy johdonmukaisena, kun kuluttajat, tuottajat, alusta, operointi, security, compliance ja business käyttävät samaa näyttöä ja päätöksiä.", - "station.integration-architecture-platform-decisions.apply_in_work": "Käytä asemakohtaisia integraatioresursseja ensisijaisena työpohjana.", - "station.integration-architecture-platform-decisions.outcomes": "Dokumentoitu integraatiopäätös tai työpohja", - "station.integration-architecture-platform-decisions.outcomes.1": "Keskeiset vastuut, näyttö ja reunaehdot selkeytetty", - "station.integration-architecture-platform-decisions.outcomes.2": "Riskit, oletukset ja seuraavat askeleet näkyvissä", - "station.integration-architecture-platform-decisions.outcomes.3": "Tulokset valmisteltu seuraavaa asemaa varten", - "station.integration-architecture-platform-decisions.how_it_works": "Selkeytä tavoite, rajaus, kuluttajat, tuottajat ja alustakonteksti.", - "station.integration-architecture-platform-decisions.how_it_works.1": "Dokumentoi relevantti näyttö, päätökset, riskit ja vastuut.", - "station.integration-architecture-platform-decisions.how_it_works.2": "Tarkista riippuvuudet arkkitehtuuriin, suunnitteluun, operointiin, julkaisuun ja seurantaan.", - "station.integration-architecture-platform-decisions.how_it_works.3": "Kirjaa avoimet asiat ja seuraavat askeleet.", - "station.integration-solution-design.title": "Integraatioratkaisun suunnittelu", - "station.integration-solution-design.description": "Integraatioratkaisun suunnittelu selkeyttää uudelleenkäytettävän integraatiokyvykkyyden seuraavat päätökset, näytön, vastuut ja riskit.", - "station.integration-solution-design.why_it_matters": "Integraatiotyö pysyy johdonmukaisena, kun kuluttajat, tuottajat, alusta, operointi, security, compliance ja business käyttävät samaa näyttöä ja päätöksiä.", - "station.integration-solution-design.apply_in_work": "Käytä asemakohtaisia integraatioresursseja ensisijaisena työpohjana.", - "station.integration-solution-design.outcomes": "Dokumentoitu integraatiopäätös tai työpohja", - "station.integration-solution-design.outcomes.1": "Keskeiset vastuut, näyttö ja reunaehdot selkeytetty", - "station.integration-solution-design.outcomes.2": "Riskit, oletukset ja seuraavat askeleet näkyvissä", - "station.integration-solution-design.outcomes.3": "Tulokset valmisteltu seuraavaa asemaa varten", - "station.integration-solution-design.how_it_works": "Selkeytä tavoite, rajaus, kuluttajat, tuottajat ja alustakonteksti.", - "station.integration-solution-design.how_it_works.1": "Dokumentoi relevantti näyttö, päätökset, riskit ja vastuut.", - "station.integration-solution-design.how_it_works.2": "Tarkista riippuvuudet arkkitehtuuriin, suunnitteluun, operointiin, julkaisuun ja seurantaan.", - "station.integration-solution-design.how_it_works.3": "Kirjaa avoimet asiat ja seuraavat askeleet.", - "station.integration-delivery-operations.title": "Integraation toimitus ja operointi", - "station.integration-delivery-operations.description": "Integraation toimitus ja operointi selkeyttää uudelleenkäytettävän integraatiokyvykkyyden seuraavat päätökset, näytön, vastuut ja riskit.", - "station.integration-delivery-operations.why_it_matters": "Integraatiotyö pysyy johdonmukaisena, kun kuluttajat, tuottajat, alusta, operointi, security, compliance ja business käyttävät samaa näyttöä ja päätöksiä.", - "station.integration-delivery-operations.apply_in_work": "Käytä asemakohtaisia integraatioresursseja ensisijaisena työpohjana.", - "station.integration-delivery-operations.outcomes": "Dokumentoitu integraatiopäätös tai työpohja", - "station.integration-delivery-operations.outcomes.1": "Keskeiset vastuut, näyttö ja reunaehdot selkeytetty", - "station.integration-delivery-operations.outcomes.2": "Riskit, oletukset ja seuraavat askeleet näkyvissä", - "station.integration-delivery-operations.outcomes.3": "Tulokset valmisteltu seuraavaa asemaa varten", - "station.integration-delivery-operations.how_it_works": "Selkeytä tavoite, rajaus, kuluttajat, tuottajat ja alustakonteksti.", - "station.integration-delivery-operations.how_it_works.1": "Dokumentoi relevantti näyttö, päätökset, riskit ja vastuut.", - "station.integration-delivery-operations.how_it_works.2": "Tarkista riippuvuudet arkkitehtuuriin, suunnitteluun, operointiin, julkaisuun ja seurantaan.", - "station.integration-delivery-operations.how_it_works.3": "Kirjaa avoimet asiat ja seuraavat askeleet.", - "station.integration-readiness-assurance.title": "Integraation valmiuden varmistus", - "station.integration-readiness-assurance.description": "Integraation valmiuden varmistus selkeyttää uudelleenkäytettävän integraatiokyvykkyyden seuraavat päätökset, näytön, vastuut ja riskit.", - "station.integration-readiness-assurance.why_it_matters": "Integraatiotyö pysyy johdonmukaisena, kun kuluttajat, tuottajat, alusta, operointi, security, compliance ja business käyttävät samaa näyttöä ja päätöksiä.", - "station.integration-readiness-assurance.apply_in_work": "Käytä asemakohtaisia integraatioresursseja ensisijaisena työpohjana.", - "station.integration-readiness-assurance.outcomes": "Dokumentoitu integraatiopäätös tai työpohja", - "station.integration-readiness-assurance.outcomes.1": "Keskeiset vastuut, näyttö ja reunaehdot selkeytetty", - "station.integration-readiness-assurance.outcomes.2": "Riskit, oletukset ja seuraavat askeleet näkyvissä", - "station.integration-readiness-assurance.outcomes.3": "Tulokset valmisteltu seuraavaa asemaa varten", - "station.integration-readiness-assurance.how_it_works": "Selkeytä tavoite, rajaus, kuluttajat, tuottajat ja alustakonteksti.", - "station.integration-readiness-assurance.how_it_works.1": "Dokumentoi relevantti näyttö, päätökset, riskit ja vastuut.", - "station.integration-readiness-assurance.how_it_works.2": "Tarkista riippuvuudet arkkitehtuuriin, suunnitteluun, operointiin, julkaisuun ja seurantaan.", - "station.integration-readiness-assurance.how_it_works.3": "Kirjaa avoimet asiat ja seuraavat askeleet.", - "station.integration-publishing-enablement.title": "Integraation julkaisu ja enablement", - "station.integration-publishing-enablement.description": "Integraation julkaisu ja enablement selkeyttää uudelleenkäytettävän integraatiokyvykkyyden seuraavat päätökset, näytön, vastuut ja riskit.", - "station.integration-publishing-enablement.why_it_matters": "Integraatiotyö pysyy johdonmukaisena, kun kuluttajat, tuottajat, alusta, operointi, security, compliance ja business käyttävät samaa näyttöä ja päätöksiä.", - "station.integration-publishing-enablement.apply_in_work": "Käytä asemakohtaisia integraatioresursseja ensisijaisena työpohjana.", - "station.integration-publishing-enablement.outcomes": "Dokumentoitu integraatiopäätös tai työpohja", - "station.integration-publishing-enablement.outcomes.1": "Keskeiset vastuut, näyttö ja reunaehdot selkeytetty", - "station.integration-publishing-enablement.outcomes.2": "Riskit, oletukset ja seuraavat askeleet näkyvissä", - "station.integration-publishing-enablement.outcomes.3": "Tulokset valmisteltu seuraavaa asemaa varten", - "station.integration-publishing-enablement.how_it_works": "Selkeytä tavoite, rajaus, kuluttajat, tuottajat ja alustakonteksti.", - "station.integration-publishing-enablement.how_it_works.1": "Dokumentoi relevantti näyttö, päätökset, riskit ja vastuut.", - "station.integration-publishing-enablement.how_it_works.2": "Tarkista riippuvuudet arkkitehtuuriin, suunnitteluun, operointiin, julkaisuun ja seurantaan.", - "station.integration-publishing-enablement.how_it_works.3": "Kirjaa avoimet asiat ja seuraavat askeleet.", - "station.integration-monitoring-improvement.title": "Integraation seuranta ja parantaminen", - "station.integration-monitoring-improvement.description": "Integraation seuranta ja parantaminen selkeyttää uudelleenkäytettävän integraatiokyvykkyyden seuraavat päätökset, näytön, vastuut ja riskit.", - "station.integration-monitoring-improvement.why_it_matters": "Integraatiotyö pysyy johdonmukaisena, kun kuluttajat, tuottajat, alusta, operointi, security, compliance ja business käyttävät samaa näyttöä ja päätöksiä.", - "station.integration-monitoring-improvement.apply_in_work": "Käytä asemakohtaisia integraatioresursseja ensisijaisena työpohjana.", - "station.integration-monitoring-improvement.outcomes": "Dokumentoitu integraatiopäätös tai työpohja", - "station.integration-monitoring-improvement.outcomes.1": "Keskeiset vastuut, näyttö ja reunaehdot selkeytetty", - "station.integration-monitoring-improvement.outcomes.2": "Riskit, oletukset ja seuraavat askeleet näkyvissä", - "station.integration-monitoring-improvement.outcomes.3": "Tulokset valmisteltu seuraavaa asemaa varten", - "station.integration-monitoring-improvement.how_it_works": "Selkeytä tavoite, rajaus, kuluttajat, tuottajat ja alustakonteksti.", - "station.integration-monitoring-improvement.how_it_works.1": "Dokumentoi relevantti näyttö, päätökset, riskit ja vastuut.", - "station.integration-monitoring-improvement.how_it_works.2": "Tarkista riippuvuudet arkkitehtuuriin, suunnitteluun, operointiin, julkaisuun ja seurantaan.", - "station.integration-monitoring-improvement.how_it_works.3": "Kirjaa avoimet asiat ja seuraavat askeleet.", - "station.capability-strategy.title": "Kyvykkyysstrategia", - "station.capability-strategy.description": "Kyvykkyysstrategia selkeyttää kyvykkyyden, kuluttajat, tuottajat, palveluodotukset, riskit, näytön ja seuraavat päätökset uudelleenkäytettävällä tasolla.", - "station.capability-strategy.why_it_matters": "Capability Cycle pysyy toteutustyylin yläpuolella ja viittaa API-, integraatio-, workflow-, datatuote- tai sovellusdetaljeihin vasta tyylipäätöksen jälkeen.", - "station.capability-strategy.apply_in_work": "", - "station.capability-strategy.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "station.capability-strategy.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "station.capability-strategy.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "station.capability-strategy.outcomes.3": "Valmis seuraavaa asemaa varten", - "station.capability-strategy.how_it_works": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "station.capability-strategy.how_it_works.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "station.capability-strategy.how_it_works.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "station.capability-strategy.how_it_works.3": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "station.capability-consumer-producer-requirements.title": "Kuluttaja-, tuottaja- ja palveluvaatimukset", - "station.capability-consumer-producer-requirements.description": "Kuluttaja-, tuottaja- ja palveluvaatimukset selkeyttää kyvykkyyden, kuluttajat, tuottajat, palveluodotukset, riskit, näytön ja seuraavat päätökset uudelleenkäytettävällä tasolla.", - "station.capability-consumer-producer-requirements.why_it_matters": "Capability Cycle pysyy toteutustyylin yläpuolella ja viittaa API-, integraatio-, workflow-, datatuote- tai sovellusdetaljeihin vasta tyylipäätöksen jälkeen.", - "station.capability-consumer-producer-requirements.apply_in_work": "", - "station.capability-consumer-producer-requirements.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "station.capability-consumer-producer-requirements.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "station.capability-consumer-producer-requirements.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "station.capability-consumer-producer-requirements.outcomes.3": "Valmis seuraavaa asemaa varten", - "station.capability-consumer-producer-requirements.how_it_works": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "station.capability-consumer-producer-requirements.how_it_works.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "station.capability-consumer-producer-requirements.how_it_works.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "station.capability-consumer-producer-requirements.how_it_works.3": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "station.capability-architecture-platform-decisions.title": "Kyvykkyyden arkkitehtuuri- ja alustapäätökset", - "station.capability-architecture-platform-decisions.description": "Kyvykkyyden arkkitehtuuri- ja alustapäätökset selkeyttää kyvykkyyden, kuluttajat, tuottajat, palveluodotukset, riskit, näytön ja seuraavat päätökset uudelleenkäytettävällä tasolla.", - "station.capability-architecture-platform-decisions.why_it_matters": "Capability Cycle pysyy toteutustyylin yläpuolella ja viittaa API-, integraatio-, workflow-, datatuote- tai sovellusdetaljeihin vasta tyylipäätöksen jälkeen.", - "station.capability-architecture-platform-decisions.apply_in_work": "", - "station.capability-architecture-platform-decisions.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "station.capability-architecture-platform-decisions.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "station.capability-architecture-platform-decisions.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "station.capability-architecture-platform-decisions.outcomes.3": "Valmis seuraavaa asemaa varten", - "station.capability-architecture-platform-decisions.how_it_works": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "station.capability-architecture-platform-decisions.how_it_works.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "station.capability-architecture-platform-decisions.how_it_works.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "station.capability-architecture-platform-decisions.how_it_works.3": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "station.capability-solution-interaction-design.title": "Kyvykkyysratkaisun ja vuorovaikutuksen suunnittelu", - "station.capability-solution-interaction-design.description": "Kyvykkyysratkaisun ja vuorovaikutuksen suunnittelu selkeyttää kyvykkyyden, kuluttajat, tuottajat, palveluodotukset, riskit, näytön ja seuraavat päätökset uudelleenkäytettävällä tasolla.", - "station.capability-solution-interaction-design.why_it_matters": "Capability Cycle pysyy toteutustyylin yläpuolella ja viittaa API-, integraatio-, workflow-, datatuote- tai sovellusdetaljeihin vasta tyylipäätöksen jälkeen.", - "station.capability-solution-interaction-design.apply_in_work": "", - "station.capability-solution-interaction-design.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "station.capability-solution-interaction-design.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "station.capability-solution-interaction-design.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "station.capability-solution-interaction-design.outcomes.3": "Valmis seuraavaa asemaa varten", - "station.capability-solution-interaction-design.how_it_works": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "station.capability-solution-interaction-design.how_it_works.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "station.capability-solution-interaction-design.how_it_works.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "station.capability-solution-interaction-design.how_it_works.3": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "station.capability-delivery-operations.title": "Kyvykkyyden toimitus ja operointi", - "station.capability-delivery-operations.description": "Kyvykkyyden toimitus ja operointi selkeyttää kyvykkyyden, kuluttajat, tuottajat, palveluodotukset, riskit, näytön ja seuraavat päätökset uudelleenkäytettävällä tasolla.", - "station.capability-delivery-operations.why_it_matters": "Capability Cycle pysyy toteutustyylin yläpuolella ja viittaa API-, integraatio-, workflow-, datatuote- tai sovellusdetaljeihin vasta tyylipäätöksen jälkeen.", - "station.capability-delivery-operations.apply_in_work": "", - "station.capability-delivery-operations.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "station.capability-delivery-operations.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "station.capability-delivery-operations.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "station.capability-delivery-operations.outcomes.3": "Valmis seuraavaa asemaa varten", - "station.capability-delivery-operations.how_it_works": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "station.capability-delivery-operations.how_it_works.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "station.capability-delivery-operations.how_it_works.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "station.capability-delivery-operations.how_it_works.3": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "station.capability-readiness-assurance.title": "Kyvykkyyden valmiuden varmistus", - "station.capability-readiness-assurance.description": "Kyvykkyyden valmiuden varmistus selkeyttää kyvykkyyden, kuluttajat, tuottajat, palveluodotukset, riskit, näytön ja seuraavat päätökset uudelleenkäytettävällä tasolla.", - "station.capability-readiness-assurance.why_it_matters": "Capability Cycle pysyy toteutustyylin yläpuolella ja viittaa API-, integraatio-, workflow-, datatuote- tai sovellusdetaljeihin vasta tyylipäätöksen jälkeen.", - "station.capability-readiness-assurance.apply_in_work": "", - "station.capability-readiness-assurance.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "station.capability-readiness-assurance.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "station.capability-readiness-assurance.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "station.capability-readiness-assurance.outcomes.3": "Valmis seuraavaa asemaa varten", - "station.capability-readiness-assurance.how_it_works": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "station.capability-readiness-assurance.how_it_works.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "station.capability-readiness-assurance.how_it_works.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "station.capability-readiness-assurance.how_it_works.3": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "station.capability-publishing-enablement.title": "Kyvykkyyden julkaisu ja enablement", - "station.capability-publishing-enablement.description": "Kyvykkyyden julkaisu ja enablement selkeyttää kyvykkyyden, kuluttajat, tuottajat, palveluodotukset, riskit, näytön ja seuraavat päätökset uudelleenkäytettävällä tasolla.", - "station.capability-publishing-enablement.why_it_matters": "Capability Cycle pysyy toteutustyylin yläpuolella ja viittaa API-, integraatio-, workflow-, datatuote- tai sovellusdetaljeihin vasta tyylipäätöksen jälkeen.", - "station.capability-publishing-enablement.apply_in_work": "", - "station.capability-publishing-enablement.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "station.capability-publishing-enablement.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "station.capability-publishing-enablement.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "station.capability-publishing-enablement.outcomes.3": "Valmis seuraavaa asemaa varten", - "station.capability-publishing-enablement.how_it_works": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "station.capability-publishing-enablement.how_it_works.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "station.capability-publishing-enablement.how_it_works.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "station.capability-publishing-enablement.how_it_works.3": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen.", - "station.capability-monitoring-improvement.title": "Kyvykkyyden seuranta ja parantaminen", - "station.capability-monitoring-improvement.description": "Kyvykkyyden seuranta ja parantaminen selkeyttää kyvykkyyden, kuluttajat, tuottajat, palveluodotukset, riskit, näytön ja seuraavat päätökset uudelleenkäytettävällä tasolla.", - "station.capability-monitoring-improvement.why_it_matters": "Capability Cycle pysyy toteutustyylin yläpuolella ja viittaa API-, integraatio-, workflow-, datatuote- tai sovellusdetaljeihin vasta tyylipäätöksen jälkeen.", - "station.capability-monitoring-improvement.apply_in_work": "", - "station.capability-monitoring-improvement.outcomes": "Dokumentoitu kyvykkyyspäätös tai työartefakti", - "station.capability-monitoring-improvement.outcomes.1": "Kuluttajat, tuottajat, omistajat, näyttö, reunaehdot ja palveluodotukset selkeytetty", - "station.capability-monitoring-improvement.outcomes.2": "Riskit, oletukset, seuraavat askeleet ja elinkaarivaikutukset näkyvissä", - "station.capability-monitoring-improvement.outcomes.3": "Valmis seuraavaa asemaa varten", - "station.capability-monitoring-improvement.how_it_works": "Selkeytä kyvykkyyden tarkoitus, kuluttajat, tuottajat, rajaus ja näyttö.", - "station.capability-monitoring-improvement.how_it_works.1": "Dokumentoi päätökset, vastuut, palveluodotukset, riskit ja tarvittavat artefaktit.", - "station.capability-monitoring-improvement.how_it_works.2": "Hyödynnä tulosta arkkitehtuurissa, suunnittelussa, toimituksessa, valmiudessa, julkaisussa tai parantamisessa.", - "station.capability-monitoring-improvement.how_it_works.3": "Käytä API-, integraatio-, workflow-, datatuote- tai sovelluskohtaista ohjeistusta vasta toteutustyylin valinnan jälkeen." + "station.monitoring-and-improving.how_it_works.3": "Oppiminen ja elinkaaripäätös: Mitkä hypoteesin oletukset vahvistuivat tai hylättiin, ja pitäisikö ratkaisua parantaa, laajentaa, rajata, suunnitella uudelleen, pysäyttää tai poistaa käytöstä?" } diff --git a/src/data/method/fr/labels.criteria.json b/src/data/method/fr/labels.criteria.json index b1532d2..be3b6cb 100644 --- a/src/data/method/fr/labels.criteria.json +++ b/src/data/method/fr/labels.criteria.json @@ -23,11 +23,11 @@ "criterion.api-documentation-ready": "La documentation et les supports d'onboarding destinés aux utilisateurs sont prêts.", "criterion.consumer-support-ready": "Les processus d'onboarding, de support et de communication sont prêts pour les utilisateurs.", "criterion.legal-compliance-clear": "Les exigences juridiques, de confidentialité et de conformité liées à la publication ou à la mise à disposition sont définies et comprises.", - "criterion.automation-opportunity-evidence-ready": "The automation hypothesis has enough referenced evidence about expected outcome, scope, initial implementation assumptions, critical risks, validation experiment, thresholds, and decision to determine whether it should proceed.", - "criterion.automation-owner-confirmed": "Ownership is clear for the automation opportunity, process decisions, PoC validation, risks, and lifecycle outcomes.", - "criterion.automation-architecture-and-controls-validated": "The selected automation architecture, implementation mechanisms, human controls, security constraints, and recovery approach have been validated with the relevant stakeholders.", - "criterion.automation-operational-readiness-confirmed": "The automation has evidence for functional correctness, permissions, exception handling, oversight, monitoring, support, rollback, and operational ownership.", - "criterion.automation-value-monitoring-ready": "Automation performance, process outcomes, risk signals, manual interventions, incidents, and realized benefits can be monitored and used to prioritize improvements.", + "criterion.automation-opportunity-evidence-ready": "L’hypothèse d’automatisation dispose de suffisamment d’éléments probants référencés sur le résultat attendu, le périmètre, les hypothèses initiales de mise en œuvre, les risques critiques, l’expérimentation de validation, les seuils et la décision pour déterminer si elle doit être poursuivie.", + "criterion.automation-owner-confirmed": "La responsabilité est claire pour l’opportunité d’automatisation, les décisions de processus, la validation du PoC, les risques et les résultats du cycle de vie.", + "criterion.automation-architecture-and-controls-validated": "L’architecture d’automatisation sélectionnée, les mécanismes de mise en œuvre, les contrôles humains, les contraintes de sécurité et l’approche de reprise ont été validés avec les parties prenantes concernées.", + "criterion.automation-operational-readiness-confirmed": "L’automatisation dispose d’éléments probants concernant l’exactitude fonctionnelle, les permissions, la gestion des exceptions, la supervision, le suivi, le support, le retour arrière et la responsabilité opérationnelle.", + "criterion.automation-value-monitoring-ready": "Les performances de l’automatisation, les résultats du processus, les signaux de risque, les interventions manuelles, les incidents et les bénéfices réalisés peuvent être suivis et utilisés pour prioriser les améliorations.", "criterion.integration-readiness-confirmed": "Les contrats d’intégration, schémas, mappings, preuves de test, environnements, permissions, identifiants, monitoring, support, replay, réconciliation, fallback, récupération, risques et responsabilités ont été revus pour la préparation à la publication.", "criterion.integration-published-for-reuse": "La capacité d’intégration est découvrable avec propriété, statut de cycle de vie, contrats, schémas, attentes de service, parcours d’accès et d’onboarding, support, versioning et canaux de feedback publiés.", "criterion.capability-readiness-confirmed": "La conception de capacité, la définition de service, les preuves de test, le modèle opérationnel, les permissions, le monitoring, le support, le fallback, les arrangements de cycle de vie, les risques et les responsabilités ont été revus pour la préparation à la publication.", diff --git a/src/data/method/fr/labels.cycles.json b/src/data/method/fr/labels.cycles.json index 7c35a6a..94ea42a 100644 --- a/src/data/method/fr/labels.cycles.json +++ b/src/data/method/fr/labels.cycles.json @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "Publication d’API", "cycle.station.monitoring-and-improving": "Suivi & amelioration API", "cycle.station.integration-capability-strategy": "Stratégie de capacité d’intégration", - "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", + "cycle.station.integration-consumer-requirements-onboarding": "Engagements du consommateur et du fournisseur d’intégration", "cycle.station.integration-architecture-decision": "Architecture d integration & decisions de plateforme", "cycle.station.integration-solution-design": "Conception de solution d’intégration", "cycle.station.integration-delivery-operations": "Livraison & opérations d’intégration", @@ -37,20 +37,6 @@ "cycle.owner.api-platform-owner": "Responsable plateforme API", "cycle.owner.integration-architect": "Architecte d’intégration", "cycle.owner.solution-architect": "Architecte solution", - "cycle.template.intent-fit.title": "Intention & adéquation", - "cycle.template.intent-fit.description": "Capturez le résultat métier, les utilisateurs, les fournisseurs, le périmètre, les contraintes et le statut de décision.", - "cycle.template.requirements.title": "Exigences", - "cycle.template.requirements.description": "Collectez les contributions d’experts à l’aide des questions recommandées. Traitez les réponses comme des entrées pour les décisions de conception, et non comme des décisions finales.", - "cycle.template.architecture-decision.title": "Décision d’architecture", - "cycle.template.architecture-decision.description": "Comparez les choix d’architecture viables par rapport aux exigences, preuves, risques et questions ouvertes.", - "cycle.template.api-architecture-decision.title": "Décision d’architecture API", - "cycle.template.api-architecture-decision.description": "Documentez les décisions relatives à l’architecture API, à la plateforme, à la sécurité, au cycle de vie et à la publication.", - "cycle.template.integration-pattern-decision.title": "Décision de modèle d’intégration", - "cycle.template.integration-pattern-decision.description": "Comparez API, événements, fichiers, flux, produits de données, intégration directe et options hybrides par rapport aux exigences.", - "cycle.template.human-validation.title": "Validation humaine", - "cycle.template.human-validation.description": "Documentez qui valide les résultats assistés par l’IA et quelles décisions nécessitent une responsabilité humaine.", - "cycle.template.adr.title": "Architecture Decision Record", - "cycle.template.adr.description": "Documentez la décision choisie, la justification, les alternatives, les conséquences, les preuves et les actions de suivi.", "cycle.api-productization-cycle.station.api-product-strategy.description": "Cadrez l’API comme un produit avec une proposition de valeur claire, des utilisateurs, un modèle économique, une responsabilité et une intention de cycle de vie.", "cycle.api-productization-cycle.station.api-consumer-experience.description": "Définissez les segments d’utilisateurs API, les parcours d’onboarding, les attentes et les exigences d’expérience avant de verrouiller les décisions de conception.", "cycle.api-productization-cycle.station.api-platform-architecture.description": "Choisissez et validez la plateforme API, l’architecture, la gouvernance et les contraintes opérationnelles nécessaires au produit.", @@ -61,7 +47,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Suivez la santé de l’API, l’adoption, les résultats utilisateurs, la fiabilité et les opportunités d’amélioration après publication.", "cycle.automation-cycle.title": "Cycle d’automatisation", "cycle.automation-cycle.description": "Un cycle pour sélectionner, concevoir, livrer, déployer et améliorer des solutions d’automatisation couvrant les personnes, règles, workflows, agents, intégrations, automatisation d’interface et opérations.", - "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", + "cycle.automation-cycle.purpose": "Guider les équipes depuis les résultats attendus pour le client externe et la capacité jusqu’à une solution d’automatisation validée, gouvernée et exploitable.", "cycle.audience.automation-owners": "Responsables automatisation", "cycle.audience.process-owners": "Responsables de processus", "cycle.audience.automation-teams": "Équipes d’automatisation", @@ -71,33 +57,33 @@ "cycle.station.automation-readiness-review": "Revue de préparation de l’automatisation", "cycle.station.automation-enablement": "Deploiement & enablement de l automatisation", "cycle.station.automation-monitoring-improvement": "Suivi & amélioration de l’automatisation", - "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", - "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", - "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", + "cycle.automation-cycle.station.api-product-strategy.description": "Partir du client externe le plus significatif. Réutiliser les éléments probants du parcours et de la valeur de capacité pour valider si une hypothèse d’automatisation doit être poursuivie.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Clarifier les exigences de processus, d’expérience, de domaine, de service et non fonctionnelles auxquelles le workflow et l’architecture ultérieurs devront répondre.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Utiliser l’impact, l’emplacement, la capacité et les exigences antérieures pour choisir l’approche de mise en œuvre de l’automatisation et consigner la justification ainsi que les risques restants.", + "cycle.automation-cycle.station.api-design.description": "Concevoir le workflow interne nécessaire pour produire les résultats client et capacité sélectionnés, y compris la répartition du travail, les contrôles, les exceptions, la reprise, les preuves et le suivi.", + "cycle.automation-cycle.station.api-delivery.description": "Construire, configurer, tester, versionner, déployer et préparer le modèle opérationnel du parcours d’automatisation sélectionné, y compris la responsabilité, les environnements, les runbooks, le suivi, les solutions de repli, le retour arrière, le support et les risques connus.", "cycle.automation-cycle.station.api-audit.description": "Utilisez une checklist de préparation pour examiner les preuves et enregistrer la décision de publication: prêt, prêt sous conditions, remédiation requise ou non approuvé.", "cycle.automation-cycle.station.api-publishing.description": "Activez et déployez l’automatisation en sécurité avec communication, formation, consignes d’exploitation, circuits de support, suivi de l’adoption, canaux de feedback, déploiement progressif, conditions de pause et de rollback.", - "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", - "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", + "cycle.automation-cycle.station.monitoring-and-improving.description": "Suivre les résultats réels de l’automatisation, les exécutions réussies et échouées, les exceptions, les nouvelles tentatives, les interventions, le temps de cycle, le temps d’attente, le coût, les erreurs, les actions non sûres, l’adoption, la confiance, le bénéfice réalisé et les hypothèses confirmées ou rejetées.", + "cycle.station.process-user-automation-requirements": "Exigences de processus et d’expérience", + "cycle.station.automation-architecture-platform-decision": "Décision d’architecture et de plateforme d’automatisation", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Partir du parcours client, de la valeur de capacité et des éléments de viabilité, puis valider si la capacité d’intégration réutilisable proposée doit être poursuivie.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Convenir des engagements du fournisseur et du consommateur concernant l’accès, la validation, le service, la gestion des défaillances, la reprise, la compatibilité et le cycle de vie.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Sélectionner l’architecture d’intégration, le style d’implémentation et les capacités plateforme en tenant compte des contraintes et de la gouvernance.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Concevoir la solution d’intégration, les contrats, schémas, structures de données, mappings et modèles d’interaction ou de livraison pour le style sélectionné.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Construire, tester, déployer et exploiter la capacité d’intégration avec son style d’implémentation sélectionné et son contrat validé.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Assurer la préparation, la gouvernance, la qualité, la sécurité, la conformité et les preuves opérationnelles d’intégration avant publication.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Publier la capacité d’intégration pour que les équipes puissent la découvrir, l’évaluer, demander l’accès, s’onboarder, la réutiliser et obtenir du support.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Surveiller fiabilité, réutilisation, incidents, performance, résultats consommateurs et besoins d’amélioration de l’intégration.", - "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", + "cycle.station.consumer-producer-service-requirements": "Engagements du consommateur et du producteur", "cycle.station.capability-architecture-platform-decisions": "Décisions d’architecture et plateforme de capacité", "cycle.station.capability-solution-interaction-design": "Conception de solution et interaction de capacité", "cycle.station.capability-delivery-operations": "Livraison et opérations de capacité", "cycle.station.capability-readiness-assurance": "Assurance de préparation de capacité", "cycle.station.capability-publishing-enablement": "Publication et enablement de capacité", "cycle.station.capability-monitoring-improvement": "Monitoring et amélioration de capacité", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Partir du parcours client, de la valeur de capacité et des éléments de viabilité, puis valider si la capacité numérique réutilisable proposée doit être poursuivie.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Convenir des engagements mutuels du propriétaire, du producteur et du consommateur concernant l’accès, le service, le support, le changement et le cycle de vie.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Décisions d’architecture et plateforme de capacité: Guide la définition d’une capacité réutilisable depuis l’hypothèse et les exigences consommateur/producteur jusqu’à l’architecture, la conception, la livraison, la préparation, la publication et l’amélioration continue.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Conception de solution et interaction de capacité: Guide la définition d’une capacité réutilisable depuis l’hypothèse et les exigences consommateur/producteur jusqu’à l’architecture, la conception, la livraison, la préparation, la publication et l’amélioration continue.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Livraison et opérations de capacité: Guide la définition d’une capacité réutilisable depuis l’hypothèse et les exigences consommateur/producteur jusqu’à l’architecture, la conception, la livraison, la préparation, la publication et l’amélioration continue.", diff --git a/src/data/method/fr/labels.resources.json b/src/data/method/fr/labels.resources.json index 4f79647..79d0900 100644 --- a/src/data/method/fr/labels.resources.json +++ b/src/data/method/fr/labels.resources.json @@ -67,7 +67,7 @@ "resource.contract-first-design.title": "Conception d’intégration contract-first", "resource.contract-first-design.description": "Guidance for validating integration contracts before delivery, including OpenAPI, AsyncAPI, event schemas, message schemas, file schemas, data contracts, and interface specifications.", "resource.contract-first-design.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Contrat de première conception »", - "resource.contract-first-design.steps": "Apply contract-first or design-first approaches to validate integration contracts before implementation.", + "resource.contract-first-design.steps": "Appliquer des approches contract-first ou design-first pour valider les contrats d’intégration avant la mise en œuvre.", "resource.contract-first-design.tips": "Adaptez cette ressource à votre contexte.", "resource.cross-functional-collaboration-best-practices.title": "Meilleures pratiques en matière de collaboration interfonctionnelle", "resource.cross-functional-collaboration-best-practices.description": "Pratiques visant à faciliter la communication et l'alignement entre les équipes commerciales et techniques lors de la planification ou de la fourniture d'API.", @@ -79,7 +79,7 @@ "resource.data-privacy-guidelines.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Lignes directrices sur la protection des données »", "resource.data-privacy-guidelines.steps": "Garantir la confidentialité des données des utilisateurs en mettant en œuvre des mesures de protection des données, telles que l'anonymisation et les contrôles d'accès.", "resource.data-privacy-guidelines.tips": "Adaptez cette ressource à votre contexte.", - "resource.domain-canvas.title": "Domain Canvas", + "resource.domain-canvas.title": "Canevas de domaine", "resource.domain-canvas.description": "Un outil de modélisation pour définir et communiquer les entités et les relations clés de votre domaine, en assurant la cohérence sémantique entre les API.", "resource.domain-canvas.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Domain Canvas »", "resource.domain-canvas.steps": "Définir les entités de base, leurs attributs et leurs relations afin de créer une compréhension conceptuelle partagée entre les API.", @@ -134,7 +134,7 @@ "resource.api-audit-checklist.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Liste de contrôle de l'audit de l'API »", "resource.api-audit-checklist.steps": "Utilisez la liste de contrôle de l'audit de l'API pour vous assurer que la conception de l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.", "resource.api-audit-checklist.tips": "Chaque élément d'audit relie les tâches du cycle de vie (étapes), les directives applicables et les preuves à l'appui afin de fournir une vision claire de l'état de préparation de l'API.", - "resource.api-business-model-canvas.title": "API Business Model Canvas", + "resource.api-business-model-canvas.title": "Canevas de modèle économique API", "resource.api-business-model-canvas.description": "Évaluer stratégiquement la viabilité de l'activité API en établissant une cartographie des propositions de valeur, des segments de consommateurs et des ressources clés.", "resource.api-business-model-canvas.outcomes": "Une stratégie commerciale claire pour les API", "resource.api-business-model-canvas.steps": "Résumer la proposition de valeur de l'API", @@ -144,47 +144,47 @@ "resource.api-design-principles.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Principes de conception de l'API »", "resource.api-design-principles.steps": "**Consumer-first design:** commencer chaque cycle APIOps en rassemblant les objectifs des utilisateurs et les termes du domaine afin que les APIs résolvent des problèmes réels.", "resource.api-design-principles.tips": "Adaptez cette ressource à votre contexte.", - "resource.api-value-proposition-canvas.title": "API Value Proposition Canvas", + "resource.api-value-proposition-canvas.title": "Canevas de proposition de valeur API", "resource.api-value-proposition-canvas.description": "Aligner les fonctionnalités de l'API sur les besoins des utilisateurs en établissant une correspondance entre les tâches, les douleurs et les gains et les produits de l'API.", "resource.api-value-proposition-canvas.outcomes": "Développement de fonctionnalités ciblées", "resource.api-value-proposition-canvas.steps": "Liste des tâches liées au parcours de l'utilisateur", "resource.api-value-proposition-canvas.tips": "Utiliser les données du Customer Journey Canvas", "resource.business-impact-canvas.title": "Canvas d’impact métier", - "resource.business-impact-canvas.description": "Assess expected benefits, operational, customer, employee, financial, compliance, strategic, risk, and not-proceeding impacts that should shape prioritization and decisions.", - "resource.business-impact-canvas.outcomes": "Documented business impact assessment", - "resource.business-impact-canvas.steps": "Identify expected business, customer, employee, quality, speed, risk, compliance, and strategic benefits.", - "resource.business-impact-canvas.tips": "Use this for value and consequence evidence, not only risk and resilience analysis.", - "resource.capacity-canvas.title": "Capacity Canvas", - "resource.capacity-canvas.description": "Quantify demand, load, timing, availability, and scaling needs for capabilities, automations, integrations, or services.", + "resource.business-impact-canvas.description": "évaluer les bénéfices attendus ainsi que les impacts opérationnels, clients, employés, financiers, de conformité, stratégiques, de risque et de non-poursuite qui doivent orienter la priorisation et les décisions.", + "resource.business-impact-canvas.outcomes": "évaluation documentée de l’impact métier", + "resource.business-impact-canvas.steps": "Identifier les bénéfices attendus pour le métier, les clients, les employés, la qualité, la rapidité, les risques, la conformité et la stratégie.", + "resource.business-impact-canvas.tips": "Utiliser ceci comme preuve de valeur et de conséquences, pas uniquement pour l’analyse des risques et de la résilience.", + "resource.capacity-canvas.title": "Canevas de capacité", + "resource.capacity-canvas.description": "Quantifier la demande, la charge, le calendrier, la disponibilité et les besoins de mise ? l’échelle pour les capacités, les automatisations, les intégrations ou les services.", "resource.capacity-canvas.outcomes": "Exigences de capacité alignées sur la demande métier attendue", - "resource.capacity-canvas.steps": "Current Business Volumes: Quantify current business volumes and transaction rates.", - "resource.capacity-canvas.tips": "Use requirements canvases to capture what users need; use this canvas to quantify demand and inform scaling decisions.", - "resource.customer-journey-canvas.title": "Customer Journey Canvas", - "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", - "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", - "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.event-canvas.title": "Event Canvas", + "resource.capacity-canvas.steps": "Volumes métier actuels : quantifier les volumes métier actuels et les taux de transaction.", + "resource.capacity-canvas.tips": "Utiliser les canevas d’exigences pour capturer les besoins des utilisateurs ; utiliser ce canevas pour quantifier la demande et éclairer les décisions de mise ? l’échelle.", + "resource.customer-journey-canvas.title": "Canevas du parcours client", + "resource.customer-journey-canvas.description": "Quel parcours le client externe le plus significatif vit-il, et que faut-il améliorer ?", + "resource.customer-journey-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.customer-journey-canvas.steps": "Commencer par le client externe le plus significatif. Décrire son parcours réel avant de remonter vers les capacités, les processus internes ou les choix de mise en œuvre.", + "resource.customer-journey-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.event-canvas.title": "Canevas d’événements", "resource.event-canvas.description": "Concevez des interfaces et intégrations événementielles en définissant les événements, déclencheurs, schémas, producteurs, utilisateurs et logiques de traitement.", "resource.event-canvas.outcomes": "Modèle d’interaction événementiel défini", "resource.event-canvas.steps": "Identifier les événements clés du système", "resource.event-canvas.tips": "Utiliser des schémas d'événements pour normaliser les formats d'événements", - "resource.graphql-canvas.title": "GraphQL Canvas", + "resource.graphql-canvas.title": "Canevas GraphQL", "resource.graphql-canvas.description": "Concevoir des API GraphQL en définissant des types, des requêtes, des mutations et des abonnements.", "resource.graphql-canvas.outcomes": "Conception d'une API GraphQL structurée", "resource.graphql-canvas.steps": "Quels sont les problèmes que les consommateurs d'API tentent de résoudre ? De quelles données ont-ils besoin ?", "resource.graphql-canvas.tips": "Utiliser l'introspection pour valider les définitions de type", - "resource.interaction-canvas.title": "Interaction Canvas", + "resource.interaction-canvas.title": "Canevas d’interaction", "resource.interaction-canvas.description": "Définir les interactions API, les flux de travail et les réponses attendues afin de garantir une expérience cohérente pour les consommateurs d'API.", "resource.interaction-canvas.outcomes": "Modèle d’interaction défini pour la capacité choisie", "resource.interaction-canvas.steps": "Associer les interactions de l'API aux tâches de l'utilisateur", "resource.interaction-canvas.tips": "Commencer par les cas d'utilisation courants avant de traiter les cas marginaux", - "resource.location-canvas.title": "Location Canvas", + "resource.location-canvas.title": "Canevas de localisation", "resource.location-canvas.description": "Cartographier les emplacements des fournisseurs d'API et des consommateurs pour garantir la conformité et les performances dans toutes les régions.", "resource.location-canvas.outcomes": "Exigences de localisation, de résidence des données, de réseau et de réglementation documentées", "resource.location-canvas.steps": "Carte des emplacements des fournisseurs d'API.", "resource.location-canvas.tips": "Collaborer avec les équipes juridiques et de conformité", - "resource.rest-canvas.title": "REST Canvas", + "resource.rest-canvas.title": "Canevas REST", "resource.rest-canvas.description": "Concevoir des API en utilisant les principes RESTful, en définissant des ressources, des verbes et des exemples de requêtes et de réponses.", "resource.rest-canvas.outcomes": "Conception cohérente de l'API RESTful", "resource.rest-canvas.steps": "Identifier les ressources clés exposées par l'API", @@ -255,8 +255,8 @@ "resource.competitor-analysis-template.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.", "resource.contract-first-design.outcomes.1": "Approche cohérente pour appliquer « Contrat de première conception »", "resource.contract-first-design.outcomes.2": "Meilleure application des pratiques associées", - "resource.contract-first-design.steps.1": "Define interface contracts, schemas, responsibilities, usage rules, examples, and lifecycle expectations.", - "resource.contract-first-design.steps.2": "Use machine-readable formats such as OpenAPI, AsyncAPI, event schemas, message schemas, file schemas, data contracts, or interface specifications where possible.", + "resource.contract-first-design.steps.1": "Définir les contrats d’interface, les schémas, les responsabilités, les règles d’utilisation, les exemples et les attentes de cycle de vie.", + "resource.contract-first-design.steps.2": "Utiliser si possible des formats lisibles par machine tels qu’OpenAPI, AsyncAPI, les schémas d’événements, les schémas de messages, les schémas de fichiers, les contrats de données ou les spécifications d’interface.", "resource.contract-first-design.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.", "resource.cross-functional-collaboration-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière de collaboration interfonctionnelle »", "resource.cross-functional-collaboration-best-practices.outcomes.2": "Meilleure application des pratiques associées", @@ -335,33 +335,33 @@ "resource.api-value-proposition-canvas.steps.3": "Cartographier les caractéristiques des produits de l'API", "resource.api-value-proposition-canvas.tips.1": "Mettre en évidence les caractéristiques qui soulagent les douleurs ou améliorent les gains", "resource.api-value-proposition-canvas.tips.2": "Valider les caractéristiques avec les consommateurs d'API pour garantir l'alignement", - "resource.business-impact-canvas.outcomes.1": "Expected value, affected groups, financial and strategic consequences, risks, and mitigations clarified", + "resource.business-impact-canvas.outcomes.1": "Valeur attendue, groupes concernés, conséquences financières et stratégiques, risques et mesures d’atténuation clarifiés", "resource.business-impact-canvas.outcomes.2": "Preuves pour les décisions d’opportunité, d’architecture, de déploiement, de préparation et de poursuite ou d’arrêt", - "resource.business-impact-canvas.steps.1": "Assess operational efficiency, customer and employee impact, financial impact, compliance impact, strategic impact, and impact of not proceeding.", + "resource.business-impact-canvas.steps.1": "évaluer l’efficacité opérationnelle, l’impact sur les clients et les employés, l’impact financier, l’impact de conformité, l’impact stratégique et l’impact de la non-poursuite.", "resource.business-impact-canvas.steps.2": "Identifiez les risques, la criticité, les atténuations, les risques résiduels et les conséquences décisionnelles.", "resource.business-impact-canvas.steps.3": "Utilisez les preuves d’impact pour orienter la priorisation, l’architecture, le déploiement, la préparation et les décisions de poursuite ou d’arrêt.", "resource.business-impact-canvas.steps.4": "Risques liés aux données : Identifier les risques pour l'exactitude ou la disponibilité des données.", "resource.business-impact-canvas.steps.5": "Moyens d'atténuer les risques liés aux données : Prévoir des stratégies pour faire face aux risques liés aux données.", - "resource.business-impact-canvas.tips.1": "Include business stakeholders, users or employees, operations, compliance, and technical stakeholders.", - "resource.business-impact-canvas.tips.2": "Record the impact of not proceeding as well as expected benefits.", + "resource.business-impact-canvas.tips.1": "Inclure les parties prenantes métier, les utilisateurs ou employés, les opérations, la conformité et les parties prenantes techniques.", + "resource.business-impact-canvas.tips.2": "Consigner l’impact de la non-poursuite ainsi que les bénéfices attendus.", "resource.capacity-canvas.outcomes.1": "Hypothèses de pics de charge, de disponibilité et de croissance documentées", "resource.capacity-canvas.outcomes.2": "Décisions de mise à l’échelle, de mise en cache et de limitation de débit définies", - "resource.capacity-canvas.steps.1": "Future Consumption Trends: Estimate future demand and growth assumptions.", - "resource.capacity-canvas.steps.2": "Peak Load and Availability Requirements: Quantify peak load and availability needs.", - "resource.capacity-canvas.steps.3": "Caching, rate limiting, and scaling approaches: Record architecture follow-up options where capacity requires them.", + "resource.capacity-canvas.steps.1": "Tendances de consommation futures : estimer la demande future et les hypothèses de croissance.", + "resource.capacity-canvas.steps.2": "Exigences de charge de pointe et de disponibilité : quantifier la charge de pointe et les besoins de disponibilité.", + "resource.capacity-canvas.steps.3": "Mise en cache, limitation de débit et approches de mise ? l’échelle : consigner les options de suivi architectural lorsque la capacité les exige.", "resource.capacity-canvas.steps.4": "Proposer des stratégies de mise à l'échelle", "resource.capacity-canvas.tips.1": "Utilisez des données mesurées lorsqu’elles sont disponibles et explicitez les hypothèses.", "resource.capacity-canvas.tips.2": "Réexaminez le canvas après les pilotes ou tout changement significatif de la demande.", - "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.customer-journey-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.customer-journey-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.customer-journey-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.customer-journey-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", "resource.customer-journey-canvas.steps.3": "Cartographier les étapes du voyage avec les intrants et les extrants", "resource.customer-journey-canvas.steps.4": "Identifier les problèmes des clients", "resource.customer-journey-canvas.steps.5": "Résumer les gains pour les clients", "resource.customer-journey-canvas.steps.6": "Définir les intrants nécessaires et les résultats qui en découlent", "resource.customer-journey-canvas.steps.7": "Définir les interactions API pour chaque étape", - "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.customer-journey-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", "resource.event-canvas.outcomes.1": "Événements, déclencheurs, schémas, producteurs et utilisateurs clarifiés", "resource.event-canvas.outcomes.2": "Attentes de traitement, d’accusé de réception et de gestion des échecs documentées", "resource.event-canvas.steps.1": "Définir des déclencheurs pour chaque événement", @@ -404,7 +404,7 @@ "resource.rest-canvas.steps.3": "Fournir des exemples de demandes et de réponses pour chaque verbe", "resource.rest-canvas.tips.1": "Veiller à ce que les URI des ressources soient intuitifs et cohérents", "resource.rest-canvas.tips.2": "Documentez la gestion des erreurs et les codes de réponse.", - "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas", + "resource.capability-value-proposition-canvas.title": "Canevas de proposition de valeur de capacité", "resource.capability-value-proposition-canvas.description": "Un canvas indépendant de la technologie pour cartographier les tâches, gains, irritants et capacités réutilisables candidates des utilisateurs avant de sélectionner un mode de mise en œuvre.", "resource.capability-value-proposition-canvas.outcomes": "Proposition de valeur claire pour une capacité réutilisable", "resource.capability-value-proposition-canvas.outcomes.1": "Tâches, gains et irritants des utilisateurs capturés sans présupposer de technologie", @@ -415,7 +415,7 @@ "resource.capability-value-proposition-canvas.steps.3": "Regroupez les caractéristiques en capacités réutilisables candidates.", "resource.capability-value-proposition-canvas.tips": "Restez indépendant de la technologie jusqu’à ce que les exigences indiquent un mode de mise en œuvre adapté.", "resource.capability-value-proposition-canvas.tips.1": "Utilisez ce canvas à la place de l’API Value Proposition Canvas lorsqu’une API n’est pas encore le mode de mise en œuvre retenu.", - "resource.capability-business-model-canvas.title": "Capability Business Model Canvas", + "resource.capability-business-model-canvas.title": "Canevas de modèle économique de capacité", "resource.capability-business-model-canvas.description": "Un business model canvas pour les capacités réutilisables, couvrant la valeur, les utilisateurs, la responsabilité, l’engagement, les coûts et les bénéfices sans présupposer de mode de mise en œuvre.", "resource.capability-business-model-canvas.outcomes": "Modèle opérationnel viable pour une capacité réutilisable", "resource.capability-business-model-canvas.outcomes.1": "Responsabilité, utilisateurs, canaux, partenaires et besoins de support clarifiés", @@ -505,9 +505,9 @@ "resource.automation-readiness-checklist.outcomes": "Décision de préparation de l’automatisation", "resource.automation-readiness-checklist.outcomes.1": "Décision de publication enregistrée comme prêt, prêt sous conditions, remédiation requise ou non approuvé", "resource.automation-readiness-checklist.outcomes.2": "Preuves, constats bloquants, risques résiduels, conditions, actions de remédiation, décideur et date de décision documentés avant publication", - "resource.automation-readiness-checklist.steps": "Review completed operating model, workflow design, business rules, controls, access, data handling, exception paths, and evidence.", + "resource.automation-readiness-checklist.steps": "Examiner le modèle opérationnel terminé, la conception du workflow, les règles métier, les contrôles, les accès, le traitement des données, les chemins d’exception et les preuves.", "resource.automation-readiness-checklist.steps.1": "Identifiez les constats bloquants, les risques résiduels acceptés, les preuves manquantes et les actions de remédiation requises.", - "resource.automation-readiness-checklist.steps.2": "Record the release decision, decision owner, decision date, conditions, and follow-up actions.", + "resource.automation-readiness-checklist.steps.2": "Consigner la décision de publication, le responsable de la décision, la date de décision, les conditions et les actions de suivi.", "resource.automation-readiness-checklist.steps.3": "Consignez les écarts, décisions et risques acceptés.", "resource.automation-rollout-enablement-guide.title": "Guide de déploiement et d’enablement", "resource.automation-rollout-enablement-guide.description": "Guide pour activer et déployer les automatisations avec analyse du travail modifié, approche de déploiement, enablement, support, feedback, suivi de l’adoption et conditions de contrôle.", @@ -542,107 +542,107 @@ "resource.api-testing-best-practices.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.", "resource.apiops-CI-CD-for-apis.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.", "resource.api-audit-checklist.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.", - "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", - "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", - "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", - "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", - "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", - "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", - "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", - "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", - "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", - "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", - "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", - "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", - "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", - "resource.user-operator-experience-requirements.outcomes.1": "Availability, timeliness, permissions, support, recovery, observability, and activation needs captured", - "resource.user-operator-experience-requirements.outcomes.2": "Constraints ready for later architecture, workflow, and capacity decisions", - "resource.user-operator-experience-requirements.steps": "Capture user, operator, approver, and support goals for the target process.", - "resource.user-operator-experience-requirements.steps.1": "Clarify availability, timeliness, volume, data quality, permissions, activation, changes, support, observability, recovery, and continuity expectations.", - "resource.user-operator-experience-requirements.steps.2": "Translate the expectations into constraints for later automation design without choosing the implementation mechanism.", - "resource.user-operator-experience-requirements.tips": "Use this label in the Automation Cycle instead of API consumer wording.", - "resource.user-operator-experience-requirements.tips.1": "Keep the shared underlying requirements canvas intact for other cycles.", - "resource.automation-monitoring-value-metrics.title": "Automation Monitoring and Value Metrics", + "resource.automation-opportunity-canvas.title": "Canevas d’hypothèse et de validation de l’automatisation", + "resource.automation-opportunity-canvas.description": "Transformer les éléments existants sur le parcours, la valeur, l’impact, le domaine et la capacité en une décision d’automatisation testable.", + "resource.automation-opportunity-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.automation-opportunity-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.automation-opportunity-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.automation-opportunity-canvas.steps": "Réutiliser les résultats des canevas précédents. Consigner uniquement l’hypothèse restante, les incertitudes, la validation et la décision.", + "resource.automation-opportunity-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.automation-opportunity-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.automation-opportunity-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.automation-opportunity-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.automation-workflow-canvas.title": "Canevas de workflow d’automatisation", + "resource.automation-workflow-canvas.description": "Concevoir le workflow interne nécessaire pour produire les résultats client et capacité sélectionnés.", + "resource.automation-workflow-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.automation-workflow-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.automation-workflow-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.automation-workflow-canvas.steps": "Réutiliser les éléments du parcours client, de la proposition de valeur, du domaine et de la validation. Définir le travail interne, le répartir entre les personnes et l’automatisation, puis ajouter uniquement les détails d’exécution.", + "resource.automation-workflow-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.automation-workflow-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.automation-workflow-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.automation-workflow-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.automation-architecture-decision-canvas.title": "Canevas de décision d’architecture d’automatisation", + "resource.automation-architecture-decision-canvas.description": "Choisir l’approche de mise en œuvre ? partir des éléments probants déjà collectés.", + "resource.automation-architecture-decision-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.automation-architecture-decision-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.automation-architecture-decision-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.automation-architecture-decision-canvas.steps": "Faire remonter les contraintes et les choix de responsabilité. Comparer uniquement les mécanismes viables, puis consigner la décision et les risques restants.", + "resource.automation-architecture-decision-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.automation-architecture-decision-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.automation-architecture-decision-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.automation-architecture-decision-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.automation-readiness-operations-canvas.title": "Canevas de préparation et d’exploitation de l’automatisation", + "resource.automation-readiness-operations-canvas.description": "Préparer les éléments probants opérationnels minimaux nécessaires avant la revue de préparation.", + "resource.automation-readiness-operations-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.automation-readiness-operations-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.automation-readiness-operations-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.automation-readiness-operations-canvas.steps": "Réutiliser les décisions de conception. Consigner la responsabilité, les dispositions opérationnelles, les preuves, la reprise et les lacunes de préparation restantes.", + "resource.automation-readiness-operations-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.automation-readiness-operations-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.automation-readiness-operations-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.automation-readiness-operations-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.user-operator-experience-requirements.title": "Exigences d’expérience utilisateur et opérateur", + "resource.user-operator-experience-requirements.description": "Une vue spécifique au cycle des exigences d’expérience, opérationnelles et non fonctionnelles pour les utilisateurs de l’automatisation, les opérateurs, les approbateurs et les équipes de support.", + "resource.user-operator-experience-requirements.outcomes": "Attentes des utilisateurs et des opérateurs clarifiées", + "resource.user-operator-experience-requirements.outcomes.1": "Besoins de disponibilité, de ponctualité, de permissions, de support, de reprise, d’observabilité et d’activation capturés", + "resource.user-operator-experience-requirements.outcomes.2": "Contraintes prêtes pour les décisions ultérieures d’architecture, de workflow et de capacité", + "resource.user-operator-experience-requirements.steps": "Capturer les objectifs des utilisateurs, des opérateurs, des approbateurs et du support pour le processus cible.", + "resource.user-operator-experience-requirements.steps.1": "Clarifier les attentes en matière de disponibilité, de ponctualité, de volume, de qualité des données, de permissions, d’activation, de changements, de support, d’observabilité, de reprise et de continuité.", + "resource.user-operator-experience-requirements.steps.2": "Traduire les attentes en contraintes pour la conception ultérieure de l’automatisation sans choisir le mécanisme de mise en œuvre.", + "resource.user-operator-experience-requirements.tips": "Utiliser ce libellé dans le Cycle d’automatisation ? la place du vocabulaire de consommateur d’API.", + "resource.user-operator-experience-requirements.tips.1": "Conserver intact le canevas d’exigences sous-jacent partagé pour les autres cycles.", + "resource.automation-monitoring-value-metrics.title": "Suivi de l’automatisation et métriques de valeur", "resource.automation-monitoring-value-metrics.description": "Guide pour mesurer les résultats, la performance opérationnelle, le comportement utilisateur, les risques, la récupération, la valeur réalisée, l’apprentissage des hypothèses et les décisions de cycle de vie après le déploiement.", - "resource.automation-monitoring-value-metrics.outcomes": "Automation monitoring, value, and learning evidence", - "resource.automation-monitoring-value-metrics.outcomes.1": "Actual outcomes, run success, failure, exception, retry, intervention, processing time, waiting time, correction, incident, adoption, and benefit signals reviewed", - "resource.automation-monitoring-value-metrics.outcomes.2": "Automation Hypothesis assumptions reviewed and improvement, expansion, redesign, or retirement decisions prioritized", - "resource.automation-monitoring-value-metrics.steps": "Outcomes and value: compare expected process, user, and business outcomes with actual evidence.", - "resource.automation-monitoring-value-metrics.steps.1": "Operational performance: review successful runs, failures, partial completions, exceptions, retries, timeouts, interventions, processing time, waiting time, and cost.", - "resource.automation-monitoring-value-metrics.steps.2": "User, risk, and recovery signals: review errors, corrections, unsafe actions, bypassing, mistrust, support needs, fallback events, and recovery failures.", - "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", + "resource.automation-monitoring-value-metrics.outcomes": "éléments probants de suivi, de valeur et d’apprentissage de l’automatisation", + "resource.automation-monitoring-value-metrics.outcomes.1": "Résultats réels, exécutions réussies, échecs, exceptions, nouvelles tentatives, interventions, temps de traitement, temps d’attente, corrections, incidents, adoption et signaux de bénéfice examinés", + "resource.automation-monitoring-value-metrics.outcomes.2": "Hypothèses de l’automatisation examinées et décisions d’amélioration, d’extension, de refonte ou de retrait priorisées", + "resource.automation-monitoring-value-metrics.steps": "Résultats et valeur : comparer les résultats attendus du processus, des utilisateurs et du métier avec les éléments réels.", + "resource.automation-monitoring-value-metrics.steps.1": "Performance opérationnelle : examiner les exécutions réussies, les échecs, les achèvements partiels, les exceptions, les nouvelles tentatives, les expirations, les interventions, le temps de traitement, le temps d’attente et le coût.", + "resource.automation-monitoring-value-metrics.steps.2": "Signaux utilisateur, de risque et de reprise : examiner les erreurs, corrections, actions non sûres, contournements, manque de confiance, besoins de support, événements de repli et échecs de reprise.", + "resource.automation-monitoring-value-metrics.steps.3": "Apprentissage et décision de cycle de vie : décider quelles hypothèses ont été confirmées ou rejetées et s’il faut améliorer, étendre, restreindre, reconcevoir, suspendre, retirer ou ajouter des éléments au backlog.", "resource.automation-monitoring-value-metrics.tips": "Le monitoring transforme les preuves opérationnelles, utilisateur, risque et valeur en décisions de cycle de vie et en backlog d’amélioration.", - "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", - "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", - "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", - "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", - "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", - "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", - "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", - "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", - "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", - "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.automation-monitoring-value-metrics.tips.1": "Inclure les signaux qui montrent l’adoption, la confiance, les besoins de supervision humaine, les besoins de reprise et la valeur réalisée.", + "resource.integration-capability-hypothesis-canvas.title": "Canevas de validation de capacité d’intégration", + "resource.integration-capability-hypothesis-canvas.description": "Valider si une capacité d’intégration réutilisable proposée doit être poursuivie.", + "resource.integration-capability-hypothesis-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.integration-capability-hypothesis-canvas.steps": "Réutiliser les éléments probants du parcours, de la valeur, du domaine, du modèle économique, de l’impact et de la capacité au lieu de les reformuler.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.integration-capability-hypothesis-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.integration-consumer-provider-requirements-canvas.title": "Canevas des engagements du consommateur et du fournisseur d’intégration", + "resource.integration-consumer-provider-requirements-canvas.description": "Convenir des responsabilités nécessaires pour utiliser et fournir une capacité d’intégration réutilisable.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.integration-consumer-provider-requirements-canvas.steps": "Faire remonter les consommateurs, les cas d’utilisation, les besoins de service et les contraintes. Consigner les engagements plutôt que redécouvrir les exigences.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.integration-architecture-decision-canvas.title": "Canevas de décision d’architecture d’intégration", + "resource.integration-architecture-decision-canvas.description": "Choisir le style d’intégration et la plateforme ? partir des éléments probants déjà collectés.", + "resource.integration-architecture-decision-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.integration-architecture-decision-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.integration-architecture-decision-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.integration-architecture-decision-canvas.steps": "Faire remonter les engagements des consommateurs, l’impact, l’emplacement et la capacité. Comparer uniquement les styles viables et consigner la décision.", + "resource.integration-architecture-decision-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.integration-architecture-decision-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.integration-architecture-decision-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.integration-architecture-decision-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.integration-readiness-operations-canvas.title": "Canevas de préparation et d’exploitation de l’intégration", + "resource.integration-readiness-operations-canvas.description": "Préparer les éléments probants opérationnels minimaux nécessaires avant la revue de préparation de l’intégration.", + "resource.integration-readiness-operations-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.integration-readiness-operations-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.integration-readiness-operations-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.integration-readiness-operations-canvas.steps": "Réutiliser les contrats et les décisions de conception. Consigner la responsabilité, les opérations, les preuves, la reprise et les lacunes de préparation restantes.", + "resource.integration-readiness-operations-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.integration-readiness-operations-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.integration-readiness-operations-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.integration-readiness-operations-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", "resource.integration-consumer-onboarding-guide.title": "Guide d’onboarding des consommateurs d’intégration", "resource.integration-consumer-onboarding-guide.description": "Guide d’onboarding des consommateurs d’intégration soutient la planification, la décision, la livraison, la publication ou l’amélioration d’une capacité d’intégration réutilisable.", "resource.integration-consumer-onboarding-guide.outcomes": "Base de travail d’intégration documentée", @@ -813,66 +813,66 @@ "resource.integration-lifecycle-management-guide.steps.2": "Utilisez les résultats pour la conception, la livraison, la préparation, la publication ou l’amélioration.", "resource.integration-lifecycle-management-guide.tips": "Adaptez cette ressource au style d’intégration choisi.", "resource.integration-lifecycle-management-guide.tips.1": "Incluez producteurs, consommateurs, plateforme, opérations, sécurité, conformité et métier.", - "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", - "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", - "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", - "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", - "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", - "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", - "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", - "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", - "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", - "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", - "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", - "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", - "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", - "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", - "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", - "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", - "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-solution-design-canvas.title": "Canevas de conception de solution d’intégration", + "resource.integration-solution-design-canvas.description": "Affiner l’architecture sélectionnée pour en faire une conception d’intégration réalisable.", + "resource.integration-solution-design-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.integration-solution-design-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.integration-solution-design-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.integration-solution-design-canvas.steps": "Réutiliser le style sélectionné, les concepts de domaine, les besoins d’interaction et les engagements. Ajouter uniquement la conception propre ? la mise en œuvre.", + "resource.integration-solution-design-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.integration-solution-design-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.integration-solution-design-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.integration-solution-design-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.capability-hypothesis-canvas.title": "Canevas de validation de capacité", + "resource.capability-hypothesis-canvas.description": "Valider si une capacité numérique réutilisable proposée doit être poursuivie.", + "resource.capability-hypothesis-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.capability-hypothesis-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.capability-hypothesis-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.capability-hypothesis-canvas.steps": "Réutiliser les résultats du parcours, de la proposition de valeur, du modèle économique, de l’impact, du domaine et de la capacité au lieu de les répéter.", + "resource.capability-hypothesis-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.capability-hypothesis-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.capability-hypothesis-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.capability-hypothesis-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.capability-consumer-producer-requirements-canvas.title": "Canevas des engagements du consommateur et du producteur de capacité", + "resource.capability-consumer-producer-requirements-canvas.description": "Convenir des engagements mutuels pour fournir et consommer une capacité réutilisable.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.capability-consumer-producer-requirements-canvas.steps": "Réutiliser les consommateurs, la valeur, les canaux, les besoins de service et la responsabilité issus des canevas précédents. Capturer uniquement les engagements convenus et les écarts.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.capability-architecture-decision-canvas.title": "Canevas de décision d’architecture de capacité", + "resource.capability-architecture-decision-canvas.description": "Choisir comment la capacité sera fournie ? partir des éléments probants déjà collectés.", + "resource.capability-architecture-decision-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.capability-architecture-decision-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.capability-architecture-decision-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.capability-architecture-decision-canvas.steps": "Faire remonter la valeur, les engagements, l’impact, l’emplacement, la capacité et les décisions de domaine. Comparer uniquement les styles de mise en œuvre viables.", + "resource.capability-architecture-decision-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.capability-architecture-decision-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.capability-architecture-decision-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.capability-architecture-decision-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.capability-solution-design-canvas.title": "Canevas de conception de solution de capacité", + "resource.capability-solution-design-canvas.description": "Affiner le style de mise en œuvre sélectionné en une conception de capacité claire pour le consommateur.", + "resource.capability-solution-design-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.capability-solution-design-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.capability-solution-design-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.capability-solution-design-canvas.steps": "Réutiliser les résultats de valeur, de domaine, d’interaction, d’engagements et d’architecture. Ajouter uniquement la conception propre ? la solution.", + "resource.capability-solution-design-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.capability-solution-design-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.capability-solution-design-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.capability-solution-design-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", + "resource.capability-readiness-operations-canvas.title": "Canevas de préparation et d’exploitation de capacité", + "resource.capability-readiness-operations-canvas.description": "Préparer les éléments probants opérationnels minimaux nécessaires avant la revue de préparation de la capacité.", + "resource.capability-readiness-operations-canvas.outcomes": "Un artefact de décision ou de conception ciblé qui réutilise les éléments probants antérieurs", + "resource.capability-readiness-operations-canvas.outcomes.1": "Les résultats des canevas précédents sont référencés plutôt que répétés", + "resource.capability-readiness-operations-canvas.outcomes.2": "La prochaine décision, étape de conception ou lacune de préparation est explicite", + "resource.capability-readiness-operations-canvas.steps": "Réutiliser le modèle économique, les engagements et la conception de solution. Consigner uniquement la responsabilité opérationnelle, les preuves, la continuité et les lacunes de préparation.", + "resource.capability-readiness-operations-canvas.steps.1": "Compléter uniquement les sections qui ajoutent une nouvelle décision ou un affinement.", + "resource.capability-readiness-operations-canvas.steps.2": "Transmettre les décisions obtenues ? la station suivante.", + "resource.capability-readiness-operations-canvas.tips": "Créer des liens vers les canevas précédents plutôt que de copier leur contenu.", + "resource.capability-readiness-operations-canvas.tips.1": "Utiliser les canevas de support uniquement lorsque les éléments probants requis n’existent pas encore.", "resource.capability-consumer-onboarding-guide.title": "Guide d’onboarding consommateur de capacité", "resource.capability-consumer-onboarding-guide.description": "Guide d’onboarding consommateur de capacité soutient l’étape de capacité concernée avec des décisions, preuves, responsabilités, risques et prochaines étapes spécifiques.", "resource.capability-consumer-onboarding-guide.outcomes": "Décision de capacité ou artefact de travail documenté", diff --git a/src/data/method/fr/labels.stations.json b/src/data/method/fr/labels.stations.json index df120e7..ee1c34a 100644 --- a/src/data/method/fr/labels.stations.json +++ b/src/data/method/fr/labels.stations.json @@ -38,20 +38,20 @@ "station.api-audit.title": "Assurance qualité & préparation", "station.api-audit.description": "Examiner la préparation à la publication à partir des preuves de conception, tests, exploitation, permissions, supervision, support, secours, rollback, risques et propriété avant l’usage en production.", "station.api-audit.why_it_matters": "Une décision formelle de préparation empêche les solutions d’automatisation d’être publiées sans preuves claires, risques acceptés, actions correctives et propriété métier et opérationnelle.", - "station.api-audit.apply_in_work": "", + "station.api-audit.apply_in_work": "Utilisez les preuves de préparation pour prendre une décision explicite go, go conditionnel ou no-go avant l’usage en production.", "station.api-audit.outcomes": "Décision formelle de préparation", "station.api-audit.how_it_works": "Examiner la conception terminée, les preuves de test, le modèle opérationnel, les permissions, identifiants, supervision, support, secours et rollback.", "station.api-publishing.title": "Publication & enablement", "station.api-publishing.description": "Accompagner les solutions publiées afin que les utilisateurs, opérateurs, équipes concernées, systèmes consommateurs, consommateurs de service et équipes support puissent les adopter en sécurité.", "station.api-publishing.why_it_matters": "Les solutions d’automatisation ne créent de la valeur après déploiement que lorsque les personnes affectées et systèmes consommateurs comprennent ce qui change, comment l’accès et l’exploitation fonctionnent, où obtenir du support et quand le déploiement doit être suspendu, étendu ou annulé.", - "station.api-publishing.apply_in_work": "", + "station.api-publishing.apply_in_work": "Planifiez le déploiement, l’enablement, le support, le feedback et le rollback afin que les solutions publiées puissent être adoptées en sécurité.", "station.api-publishing.outcomes": "Plan de déploiement et d’enablement sécurisé", "station.api-publishing.how_it_works": "Personnes affectées et travail modifié : qui utilisera, exploitera, supportera, approuvera, consommera ou sera affecté par la publication, et quelles responsabilités, décisions, passages de relais ou pratiques de travail changeront?", "station.monitoring-and-improving.title": "Suivi & amélioration", - "station.monitoring-and-improving.description": "Monitor actual outcomes, operational performance, user behavior, risk, recovery, realized value, and improvement opportunities after release.", + "station.monitoring-and-improving.description": "Suivre après publication les résultats réels, la performance opérationnelle, le comportement des utilisateurs, les risques, la reprise, la valeur réalisée et les opportunités d’amélioration.", "station.monitoring-and-improving.why_it_matters": "Les solutions publiées ont besoin de preuves montrant si les résultats attendus sont atteints, où une intervention manuelle ou une récupération reste nécessaire, et quelle décision de cycle de vie prendre ensuite.", - "station.monitoring-and-improving.apply_in_work": "", - "station.monitoring-and-improving.outcomes": "Measured outcome, performance, risk, recovery, and value evidence", + "station.monitoring-and-improving.apply_in_work": "Utilisez les preuves opérationnelles, utilisateur, de risque et de valeur pour décider ce qu’il faut améliorer, étendre, restreindre, suspendre ou retirer.", + "station.monitoring-and-improving.outcomes": "Éléments probants mesurés sur les résultats, la performance, les risques, la reprise et la valeur", "station.monitoring-and-improving.how_it_works": "Résultats et valeur : les résultats attendus de processus, utilisateurs et métier sont-ils atteints?", "station.user-experience.title": "Expérience utilisateur - Concevoir des API en pensant à l'utilisateur", "station.user-experience.description": "Veiller à ce que les API soient conçues en pensant à l'utilisateur final, en lui offrant une expérience transparente et intuitive.", @@ -236,17 +236,17 @@ "station.api-delivery.how_it_works.5": "Utilisez la liste de contrôle de l'audit de l'API pour vous assurer que l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.", "station.api-audit.outcomes.1": "Preuves, constats bloquants, risques résiduels acceptés et actions de remédiation examinés", "station.api-audit.outcomes.2": "Décision de publication enregistrée comme prêt, prêt sous conditions, remédiation requise ou non approuvé", - "station.api-audit.outcomes.3": "Business and operational ownership confirmed before release", + "station.api-audit.outcomes.3": "Responsabilité métier et opérationnelle confirmée avant la publication", "station.api-audit.how_it_works.1": "Vérifier que les risques connus, exceptions, actions dangereuses, supervision humaine, exigences de conformité et hypothèses non résolues ont été traités ou explicitement acceptés.", "station.api-audit.how_it_works.2": "Consigner les constats bloquants, risques résiduels acceptés, conditions de publication et actions correctives requises.", "station.api-publishing.outcomes.1": "Personnes concernées, responsabilités modifiées, décisions, handoffs et pratiques de travail compris", "station.api-publishing.outcomes.2": "Activation, accès, permissions, approche de déploiement, enablement et support préparés", - "station.api-publishing.outcomes.3": "Feedback, adoption, trust, issue handling, pause, rollback, manual operation, and expansion controls defined", + "station.api-publishing.outcomes.3": "Feedback, adoption, confiance, gestion des problèmes, pause, retour arrière, fonctionnement manuel et contrôles d’extension définis", "station.api-publishing.how_it_works.1": "Activation et approche de déploiement : comment gérer l’accès, les permissions, le pilote, le déploiement progressif, les groupes restreints, le fonctionnement en parallèle et l’extension?", "station.api-publishing.how_it_works.2": "Enablement et support : quelles communications, formations, instructions opérationnelles et voies de support sont nécessaires?", - "station.monitoring-and-improving.outcomes.1": "Expected outcomes, run performance, user behavior, risks, support needs, and realized value reviewed", - "station.monitoring-and-improving.outcomes.2": "Hypothesis assumptions and lifecycle options assessed", - "station.monitoring-and-improving.outcomes.3": "Improvement backlog informed by operational, user, risk, and value evidence", + "station.monitoring-and-improving.outcomes.1": "Résultats attendus, performance d’exécution, comportement des utilisateurs, risques, besoins de support et valeur réalisée examinés", + "station.monitoring-and-improving.outcomes.2": "Hypothèses et options de cycle de vie évaluées", + "station.monitoring-and-improving.outcomes.3": "Backlog d’amélioration alimenté par les éléments probants opérationnels, utilisateur, de risque et de valeur", "station.monitoring-and-improving.how_it_works.1": "Performance opérationnelle : que montrent les exécutions réussies, échecs, achèvements partiels, exceptions, reprises, délais, interventions, temps de traitement, temps d’attente et coûts?", "station.monitoring-and-improving.how_it_works.2": "Signaux utilisateur, risque et récupération : quelles erreurs, corrections, actions dangereuses, contournements, défiance, besoins de support, événements de secours ou échecs de récupération apparaissent?", "station.user-experience.outcomes.1": "Interfaces utilisateur intuitives et cohérentes", @@ -468,197 +468,5 @@ "station.api-audit.how_it_works.4": "Consigner le responsable de décision, la date de décision et les preuves utilisées.", "station.api-audit.how_it_works.5": "Confirmer que rien ne passe en publication sans propriété métier et opérationnelle claire.", "station.api-publishing.how_it_works.3": "Feedback et contrôle : comment surveiller l’adoption, la confiance, l’usage réel, les problèmes et comportements inattendus, et quelles conditions déclenchent pause, rollback ou retour au manuel?", - "station.monitoring-and-improving.how_it_works.3": "Apprentissage et décision de cycle de vie : quelles hypothèses ont été confirmées ou rejetées, et faut-il améliorer, étendre, restreindre, reconcevoir, suspendre ou retirer la solution?", - "station.integration-capability-strategy.title": "Stratégie de capacité d’intégration", - "station.integration-capability-strategy.description": "Stratégie de capacité d’intégration clarifie les prochaines décisions, preuves, responsabilités et risques pour une capacité d’intégration réutilisable. Utilisez les canvases de support uniquement lorsque les preuves nécessaires n’existent pas déjà.", - "station.integration-capability-strategy.why_it_matters": "Le travail d’intégration reste cohérent lorsque consommateurs, producteurs, plateforme, opérations, sécurité, conformité et métier utilisent les mêmes preuves et décisions.", - "station.integration-capability-strategy.apply_in_work": "Utilisez les ressources d’intégration propres à la station comme base de travail principale.", - "station.integration-capability-strategy.outcomes": "Décision ou base de travail d’intégration documentée", - "station.integration-capability-strategy.outcomes.1": "Responsabilités, preuves et contraintes pertinentes clarifiées", - "station.integration-capability-strategy.outcomes.2": "Risques, hypothèses et prochaines étapes visibles", - "station.integration-capability-strategy.outcomes.3": "Résultats préparés pour la station suivante", - "station.integration-capability-strategy.how_it_works": "Clarifiez l’objectif, le périmètre, les consommateurs, les producteurs et le contexte plateforme.", - "station.integration-capability-strategy.how_it_works.1": "Documentez les preuves, décisions, risques et responsabilités pertinents.", - "station.integration-capability-strategy.how_it_works.2": "Vérifiez les dépendances avec architecture, conception, opérations, publication et monitoring.", - "station.integration-capability-strategy.how_it_works.3": "Consignez les points ouverts et prochaines étapes.", - "station.integration-consumer-requirements-onboarding.title": "Exigences consommateurs et onboarding d’intégration", - "station.integration-consumer-requirements-onboarding.description": "Exigences consommateurs et onboarding d’intégration clarifie les prochaines décisions, preuves, responsabilités et risques pour une capacité d’intégration réutilisable.", - "station.integration-consumer-requirements-onboarding.why_it_matters": "Le travail d’intégration reste cohérent lorsque consommateurs, producteurs, plateforme, opérations, sécurité, conformité et métier utilisent les mêmes preuves et décisions.", - "station.integration-consumer-requirements-onboarding.apply_in_work": "Utilisez les ressources d’intégration propres à la station comme base de travail principale.", - "station.integration-consumer-requirements-onboarding.outcomes": "Décision ou base de travail d’intégration documentée", - "station.integration-consumer-requirements-onboarding.outcomes.1": "Responsabilités, preuves et contraintes pertinentes clarifiées", - "station.integration-consumer-requirements-onboarding.outcomes.2": "Risques, hypothèses et prochaines étapes visibles", - "station.integration-consumer-requirements-onboarding.outcomes.3": "Résultats préparés pour la station suivante", - "station.integration-consumer-requirements-onboarding.how_it_works": "Clarifiez l’objectif, le périmètre, les consommateurs, les producteurs et le contexte plateforme.", - "station.integration-consumer-requirements-onboarding.how_it_works.1": "Documentez les preuves, décisions, risques et responsabilités pertinents.", - "station.integration-consumer-requirements-onboarding.how_it_works.2": "Vérifiez les dépendances avec architecture, conception, opérations, publication et monitoring.", - "station.integration-consumer-requirements-onboarding.how_it_works.3": "Consignez les points ouverts et prochaines étapes.", - "station.integration-architecture-platform-decisions.title": "Décisions d’architecture et plateforme d’intégration", - "station.integration-architecture-platform-decisions.description": "Décisions d’architecture et plateforme d’intégration clarifie les prochaines décisions, preuves, responsabilités et risques pour une capacité d’intégration réutilisable.", - "station.integration-architecture-platform-decisions.why_it_matters": "Le travail d’intégration reste cohérent lorsque consommateurs, producteurs, plateforme, opérations, sécurité, conformité et métier utilisent les mêmes preuves et décisions.", - "station.integration-architecture-platform-decisions.apply_in_work": "Utilisez les ressources d’intégration propres à la station comme base de travail principale.", - "station.integration-architecture-platform-decisions.outcomes": "Décision ou base de travail d’intégration documentée", - "station.integration-architecture-platform-decisions.outcomes.1": "Responsabilités, preuves et contraintes pertinentes clarifiées", - "station.integration-architecture-platform-decisions.outcomes.2": "Risques, hypothèses et prochaines étapes visibles", - "station.integration-architecture-platform-decisions.outcomes.3": "Résultats préparés pour la station suivante", - "station.integration-architecture-platform-decisions.how_it_works": "Clarifiez l’objectif, le périmètre, les consommateurs, les producteurs et le contexte plateforme.", - "station.integration-architecture-platform-decisions.how_it_works.1": "Documentez les preuves, décisions, risques et responsabilités pertinents.", - "station.integration-architecture-platform-decisions.how_it_works.2": "Vérifiez les dépendances avec architecture, conception, opérations, publication et monitoring.", - "station.integration-architecture-platform-decisions.how_it_works.3": "Consignez les points ouverts et prochaines étapes.", - "station.integration-solution-design.title": "Conception de solution d’intégration", - "station.integration-solution-design.description": "Conception de solution d’intégration clarifie les prochaines décisions, preuves, responsabilités et risques pour une capacité d’intégration réutilisable.", - "station.integration-solution-design.why_it_matters": "Le travail d’intégration reste cohérent lorsque consommateurs, producteurs, plateforme, opérations, sécurité, conformité et métier utilisent les mêmes preuves et décisions.", - "station.integration-solution-design.apply_in_work": "Utilisez les ressources d’intégration propres à la station comme base de travail principale.", - "station.integration-solution-design.outcomes": "Décision ou base de travail d’intégration documentée", - "station.integration-solution-design.outcomes.1": "Responsabilités, preuves et contraintes pertinentes clarifiées", - "station.integration-solution-design.outcomes.2": "Risques, hypothèses et prochaines étapes visibles", - "station.integration-solution-design.outcomes.3": "Résultats préparés pour la station suivante", - "station.integration-solution-design.how_it_works": "Clarifiez l’objectif, le périmètre, les consommateurs, les producteurs et le contexte plateforme.", - "station.integration-solution-design.how_it_works.1": "Documentez les preuves, décisions, risques et responsabilités pertinents.", - "station.integration-solution-design.how_it_works.2": "Vérifiez les dépendances avec architecture, conception, opérations, publication et monitoring.", - "station.integration-solution-design.how_it_works.3": "Consignez les points ouverts et prochaines étapes.", - "station.integration-delivery-operations.title": "Livraison et opérations d’intégration", - "station.integration-delivery-operations.description": "Livraison et opérations d’intégration clarifie les prochaines décisions, preuves, responsabilités et risques pour une capacité d’intégration réutilisable.", - "station.integration-delivery-operations.why_it_matters": "Le travail d’intégration reste cohérent lorsque consommateurs, producteurs, plateforme, opérations, sécurité, conformité et métier utilisent les mêmes preuves et décisions.", - "station.integration-delivery-operations.apply_in_work": "Utilisez les ressources d’intégration propres à la station comme base de travail principale.", - "station.integration-delivery-operations.outcomes": "Décision ou base de travail d’intégration documentée", - "station.integration-delivery-operations.outcomes.1": "Responsabilités, preuves et contraintes pertinentes clarifiées", - "station.integration-delivery-operations.outcomes.2": "Risques, hypothèses et prochaines étapes visibles", - "station.integration-delivery-operations.outcomes.3": "Résultats préparés pour la station suivante", - "station.integration-delivery-operations.how_it_works": "Clarifiez l’objectif, le périmètre, les consommateurs, les producteurs et le contexte plateforme.", - "station.integration-delivery-operations.how_it_works.1": "Documentez les preuves, décisions, risques et responsabilités pertinents.", - "station.integration-delivery-operations.how_it_works.2": "Vérifiez les dépendances avec architecture, conception, opérations, publication et monitoring.", - "station.integration-delivery-operations.how_it_works.3": "Consignez les points ouverts et prochaines étapes.", - "station.integration-readiness-assurance.title": "Assurance de préparation de l’intégration", - "station.integration-readiness-assurance.description": "Assurance de préparation de l’intégration clarifie les prochaines décisions, preuves, responsabilités et risques pour une capacité d’intégration réutilisable.", - "station.integration-readiness-assurance.why_it_matters": "Le travail d’intégration reste cohérent lorsque consommateurs, producteurs, plateforme, opérations, sécurité, conformité et métier utilisent les mêmes preuves et décisions.", - "station.integration-readiness-assurance.apply_in_work": "Utilisez les ressources d’intégration propres à la station comme base de travail principale.", - "station.integration-readiness-assurance.outcomes": "Décision ou base de travail d’intégration documentée", - "station.integration-readiness-assurance.outcomes.1": "Responsabilités, preuves et contraintes pertinentes clarifiées", - "station.integration-readiness-assurance.outcomes.2": "Risques, hypothèses et prochaines étapes visibles", - "station.integration-readiness-assurance.outcomes.3": "Résultats préparés pour la station suivante", - "station.integration-readiness-assurance.how_it_works": "Clarifiez l’objectif, le périmètre, les consommateurs, les producteurs et le contexte plateforme.", - "station.integration-readiness-assurance.how_it_works.1": "Documentez les preuves, décisions, risques et responsabilités pertinents.", - "station.integration-readiness-assurance.how_it_works.2": "Vérifiez les dépendances avec architecture, conception, opérations, publication et monitoring.", - "station.integration-readiness-assurance.how_it_works.3": "Consignez les points ouverts et prochaines étapes.", - "station.integration-publishing-enablement.title": "Publication et enablement de l’intégration", - "station.integration-publishing-enablement.description": "Publication et enablement de l’intégration clarifie les prochaines décisions, preuves, responsabilités et risques pour une capacité d’intégration réutilisable.", - "station.integration-publishing-enablement.why_it_matters": "Le travail d’intégration reste cohérent lorsque consommateurs, producteurs, plateforme, opérations, sécurité, conformité et métier utilisent les mêmes preuves et décisions.", - "station.integration-publishing-enablement.apply_in_work": "Utilisez les ressources d’intégration propres à la station comme base de travail principale.", - "station.integration-publishing-enablement.outcomes": "Décision ou base de travail d’intégration documentée", - "station.integration-publishing-enablement.outcomes.1": "Responsabilités, preuves et contraintes pertinentes clarifiées", - "station.integration-publishing-enablement.outcomes.2": "Risques, hypothèses et prochaines étapes visibles", - "station.integration-publishing-enablement.outcomes.3": "Résultats préparés pour la station suivante", - "station.integration-publishing-enablement.how_it_works": "Clarifiez l’objectif, le périmètre, les consommateurs, les producteurs et le contexte plateforme.", - "station.integration-publishing-enablement.how_it_works.1": "Documentez les preuves, décisions, risques et responsabilités pertinents.", - "station.integration-publishing-enablement.how_it_works.2": "Vérifiez les dépendances avec architecture, conception, opérations, publication et monitoring.", - "station.integration-publishing-enablement.how_it_works.3": "Consignez les points ouverts et prochaines étapes.", - "station.integration-monitoring-improvement.title": "Monitoring et amélioration de l’intégration", - "station.integration-monitoring-improvement.description": "Monitoring et amélioration de l’intégration clarifie les prochaines décisions, preuves, responsabilités et risques pour une capacité d’intégration réutilisable.", - "station.integration-monitoring-improvement.why_it_matters": "Le travail d’intégration reste cohérent lorsque consommateurs, producteurs, plateforme, opérations, sécurité, conformité et métier utilisent les mêmes preuves et décisions.", - "station.integration-monitoring-improvement.apply_in_work": "Utilisez les ressources d’intégration propres à la station comme base de travail principale.", - "station.integration-monitoring-improvement.outcomes": "Décision ou base de travail d’intégration documentée", - "station.integration-monitoring-improvement.outcomes.1": "Responsabilités, preuves et contraintes pertinentes clarifiées", - "station.integration-monitoring-improvement.outcomes.2": "Risques, hypothèses et prochaines étapes visibles", - "station.integration-monitoring-improvement.outcomes.3": "Résultats préparés pour la station suivante", - "station.integration-monitoring-improvement.how_it_works": "Clarifiez l’objectif, le périmètre, les consommateurs, les producteurs et le contexte plateforme.", - "station.integration-monitoring-improvement.how_it_works.1": "Documentez les preuves, décisions, risques et responsabilités pertinents.", - "station.integration-monitoring-improvement.how_it_works.2": "Vérifiez les dépendances avec architecture, conception, opérations, publication et monitoring.", - "station.integration-monitoring-improvement.how_it_works.3": "Consignez les points ouverts et prochaines étapes.", - "station.capability-strategy.title": "Stratégie de capacité", - "station.capability-strategy.description": "Stratégie de capacité clarifie la capacité, les consommateurs, producteurs, attentes de service, risques, preuves et prochaines décisions au niveau réutilisable.", - "station.capability-strategy.why_it_matters": "Le Capability Cycle reste au-dessus du style d’implémentation et ne renvoie aux détails API, intégration, workflow, produit de données ou application qu’après la décision de style.", - "station.capability-strategy.apply_in_work": "", - "station.capability-strategy.outcomes": "Décision de capacité ou artefact de travail documenté", - "station.capability-strategy.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "station.capability-strategy.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "station.capability-strategy.outcomes.3": "Résultats préparés pour la station suivante", - "station.capability-strategy.how_it_works": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "station.capability-strategy.how_it_works.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "station.capability-strategy.how_it_works.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "station.capability-strategy.how_it_works.3": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "station.capability-consumer-producer-requirements.title": "Exigences consommateur, producteur et service", - "station.capability-consumer-producer-requirements.description": "Exigences consommateur, producteur et service clarifie la capacité, les consommateurs, producteurs, attentes de service, risques, preuves et prochaines décisions au niveau réutilisable.", - "station.capability-consumer-producer-requirements.why_it_matters": "Le Capability Cycle reste au-dessus du style d’implémentation et ne renvoie aux détails API, intégration, workflow, produit de données ou application qu’après la décision de style.", - "station.capability-consumer-producer-requirements.apply_in_work": "", - "station.capability-consumer-producer-requirements.outcomes": "Décision de capacité ou artefact de travail documenté", - "station.capability-consumer-producer-requirements.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "station.capability-consumer-producer-requirements.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "station.capability-consumer-producer-requirements.outcomes.3": "Résultats préparés pour la station suivante", - "station.capability-consumer-producer-requirements.how_it_works": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "station.capability-consumer-producer-requirements.how_it_works.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "station.capability-consumer-producer-requirements.how_it_works.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "station.capability-consumer-producer-requirements.how_it_works.3": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "station.capability-architecture-platform-decisions.title": "Décisions d’architecture et plateforme de capacité", - "station.capability-architecture-platform-decisions.description": "Décisions d’architecture et plateforme de capacité clarifie la capacité, les consommateurs, producteurs, attentes de service, risques, preuves et prochaines décisions au niveau réutilisable.", - "station.capability-architecture-platform-decisions.why_it_matters": "Le Capability Cycle reste au-dessus du style d’implémentation et ne renvoie aux détails API, intégration, workflow, produit de données ou application qu’après la décision de style.", - "station.capability-architecture-platform-decisions.apply_in_work": "", - "station.capability-architecture-platform-decisions.outcomes": "Décision de capacité ou artefact de travail documenté", - "station.capability-architecture-platform-decisions.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "station.capability-architecture-platform-decisions.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "station.capability-architecture-platform-decisions.outcomes.3": "Résultats préparés pour la station suivante", - "station.capability-architecture-platform-decisions.how_it_works": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "station.capability-architecture-platform-decisions.how_it_works.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "station.capability-architecture-platform-decisions.how_it_works.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "station.capability-architecture-platform-decisions.how_it_works.3": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "station.capability-solution-interaction-design.title": "Conception de solution et interaction de capacité", - "station.capability-solution-interaction-design.description": "Conception de solution et interaction de capacité clarifie la capacité, les consommateurs, producteurs, attentes de service, risques, preuves et prochaines décisions au niveau réutilisable.", - "station.capability-solution-interaction-design.why_it_matters": "Le Capability Cycle reste au-dessus du style d’implémentation et ne renvoie aux détails API, intégration, workflow, produit de données ou application qu’après la décision de style.", - "station.capability-solution-interaction-design.apply_in_work": "", - "station.capability-solution-interaction-design.outcomes": "Décision de capacité ou artefact de travail documenté", - "station.capability-solution-interaction-design.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "station.capability-solution-interaction-design.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "station.capability-solution-interaction-design.outcomes.3": "Résultats préparés pour la station suivante", - "station.capability-solution-interaction-design.how_it_works": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "station.capability-solution-interaction-design.how_it_works.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "station.capability-solution-interaction-design.how_it_works.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "station.capability-solution-interaction-design.how_it_works.3": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "station.capability-delivery-operations.title": "Livraison et opérations de capacité", - "station.capability-delivery-operations.description": "Livraison et opérations de capacité clarifie la capacité, les consommateurs, producteurs, attentes de service, risques, preuves et prochaines décisions au niveau réutilisable.", - "station.capability-delivery-operations.why_it_matters": "Le Capability Cycle reste au-dessus du style d’implémentation et ne renvoie aux détails API, intégration, workflow, produit de données ou application qu’après la décision de style.", - "station.capability-delivery-operations.apply_in_work": "", - "station.capability-delivery-operations.outcomes": "Décision de capacité ou artefact de travail documenté", - "station.capability-delivery-operations.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "station.capability-delivery-operations.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "station.capability-delivery-operations.outcomes.3": "Résultats préparés pour la station suivante", - "station.capability-delivery-operations.how_it_works": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "station.capability-delivery-operations.how_it_works.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "station.capability-delivery-operations.how_it_works.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "station.capability-delivery-operations.how_it_works.3": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "station.capability-readiness-assurance.title": "Assurance de préparation de capacité", - "station.capability-readiness-assurance.description": "Assurance de préparation de capacité clarifie la capacité, les consommateurs, producteurs, attentes de service, risques, preuves et prochaines décisions au niveau réutilisable.", - "station.capability-readiness-assurance.why_it_matters": "Le Capability Cycle reste au-dessus du style d’implémentation et ne renvoie aux détails API, intégration, workflow, produit de données ou application qu’après la décision de style.", - "station.capability-readiness-assurance.apply_in_work": "", - "station.capability-readiness-assurance.outcomes": "Décision de capacité ou artefact de travail documenté", - "station.capability-readiness-assurance.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "station.capability-readiness-assurance.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "station.capability-readiness-assurance.outcomes.3": "Résultats préparés pour la station suivante", - "station.capability-readiness-assurance.how_it_works": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "station.capability-readiness-assurance.how_it_works.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "station.capability-readiness-assurance.how_it_works.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "station.capability-readiness-assurance.how_it_works.3": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "station.capability-publishing-enablement.title": "Publication et enablement de capacité", - "station.capability-publishing-enablement.description": "Publication et enablement de capacité clarifie la capacité, les consommateurs, producteurs, attentes de service, risques, preuves et prochaines décisions au niveau réutilisable.", - "station.capability-publishing-enablement.why_it_matters": "Le Capability Cycle reste au-dessus du style d’implémentation et ne renvoie aux détails API, intégration, workflow, produit de données ou application qu’après la décision de style.", - "station.capability-publishing-enablement.apply_in_work": "", - "station.capability-publishing-enablement.outcomes": "Décision de capacité ou artefact de travail documenté", - "station.capability-publishing-enablement.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "station.capability-publishing-enablement.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "station.capability-publishing-enablement.outcomes.3": "Résultats préparés pour la station suivante", - "station.capability-publishing-enablement.how_it_works": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "station.capability-publishing-enablement.how_it_works.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "station.capability-publishing-enablement.how_it_works.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "station.capability-publishing-enablement.how_it_works.3": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation.", - "station.capability-monitoring-improvement.title": "Monitoring et amélioration de capacité", - "station.capability-monitoring-improvement.description": "Monitoring et amélioration de capacité clarifie la capacité, les consommateurs, producteurs, attentes de service, risques, preuves et prochaines décisions au niveau réutilisable.", - "station.capability-monitoring-improvement.why_it_matters": "Le Capability Cycle reste au-dessus du style d’implémentation et ne renvoie aux détails API, intégration, workflow, produit de données ou application qu’après la décision de style.", - "station.capability-monitoring-improvement.apply_in_work": "", - "station.capability-monitoring-improvement.outcomes": "Décision de capacité ou artefact de travail documenté", - "station.capability-monitoring-improvement.outcomes.1": "Consommateurs, producteurs, propriétaires, preuves, contraintes et attentes de service clarifiés", - "station.capability-monitoring-improvement.outcomes.2": "Risques, hypothèses, prochaines étapes et impacts de cycle de vie visibles", - "station.capability-monitoring-improvement.outcomes.3": "Résultats préparés pour la station suivante", - "station.capability-monitoring-improvement.how_it_works": "Clarifiez l’objectif de la capacité, les consommateurs, producteurs, périmètre et preuves.", - "station.capability-monitoring-improvement.how_it_works.1": "Documentez décisions, responsabilités, attentes de service, risques et artefacts nécessaires.", - "station.capability-monitoring-improvement.how_it_works.2": "Utilisez le résultat pour architecture, conception, livraison, préparation, publication ou amélioration.", - "station.capability-monitoring-improvement.how_it_works.3": "Utilisez les guides API, intégration, workflow, produit de données ou application seulement après le choix du style d’implémentation." + "station.monitoring-and-improving.how_it_works.3": "Apprentissage et décision de cycle de vie : quelles hypothèses ont été confirmées ou rejetées, et faut-il améliorer, étendre, restreindre, reconcevoir, suspendre ou retirer la solution?" } diff --git a/src/data/method/pt/labels.criteria.json b/src/data/method/pt/labels.criteria.json index 9116a36..c7e4caa 100644 --- a/src/data/method/pt/labels.criteria.json +++ b/src/data/method/pt/labels.criteria.json @@ -23,11 +23,11 @@ "criterion.api-documentation-ready": "A documentação orientada para os utilizadores e os materiais de onboarding estão prontos.", "criterion.consumer-support-ready": "Os processos de onboarding, suporte e comunicação para utilizadores estão prontos.", "criterion.legal-compliance-clear": "Os requisitos legais, de privacidade e de conformidade para publicação ou disponibilização estão definidos e compreendidos.", - "criterion.automation-opportunity-evidence-ready": "The automation hypothesis has enough referenced evidence about expected outcome, scope, initial implementation assumptions, critical risks, validation experiment, thresholds, and decision to determine whether it should proceed.", - "criterion.automation-owner-confirmed": "Ownership is clear for the automation opportunity, process decisions, PoC validation, risks, and lifecycle outcomes.", - "criterion.automation-architecture-and-controls-validated": "The selected automation architecture, implementation mechanisms, human controls, security constraints, and recovery approach have been validated with the relevant stakeholders.", - "criterion.automation-operational-readiness-confirmed": "The automation has evidence for functional correctness, permissions, exception handling, oversight, monitoring, support, rollback, and operational ownership.", - "criterion.automation-value-monitoring-ready": "Automation performance, process outcomes, risk signals, manual interventions, incidents, and realized benefits can be monitored and used to prioritize improvements.", + "criterion.automation-opportunity-evidence-ready": "A hipótese de automação tem evidência referenciada suficiente sobre o resultado esperado, o âmbito, as hipóteses iniciais de implementação, os riscos críticos, a experiência de validação, os limiares e a decisão para determinar se deve avançar.", + "criterion.automation-owner-confirmed": "A propriedade está clara para a oportunidade de automação, as decisões de processo, a validação do PoC, os riscos e os resultados do ciclo de vida.", + "criterion.automation-architecture-and-controls-validated": "A arquitetura de automação selecionada, os mecanismos de implementação, os controlos humanos, as restrições de segurança e a abordagem de recuperação foram validados com as partes interessadas relevantes.", + "criterion.automation-operational-readiness-confirmed": "A automação tem evidência de correção funcional, permissões, tratamento de exceções, supervisão, monitorização, suporte, rollback e propriedade operacional.", + "criterion.automation-value-monitoring-ready": "O desempenho da automação, os resultados do processo, os sinais de risco, as intervenções manuais, os incidentes e os benefícios realizados podem ser monitorizados e usados para priorizar melhorias.", "criterion.integration-readiness-confirmed": "Contratos de integração, esquemas, mapeamentos, evidências de teste, ambientes, permissões, credenciais, monitorização, suporte, replay, reconciliação, fallback, recuperação, riscos e ownership foram revistos para prontidão de lançamento.", "criterion.integration-published-for-reuse": "A capacidade de integração está descobrível com ownership, estado de ciclo de vida, contratos, esquemas, expectativas de serviço, caminhos de acesso e onboarding, suporte, versionamento e canais de feedback publicados.", "criterion.capability-readiness-confirmed": "O desenho da capacidade, definição de serviço, evidências de teste, modelo operacional, permissões, monitorização, suporte, fallback, arranjos de ciclo de vida, riscos e ownership foram revistos para prontidão de lançamento.", diff --git a/src/data/method/pt/labels.cycles.json b/src/data/method/pt/labels.cycles.json index 89bc7ef..a8d0ccb 100644 --- a/src/data/method/pt/labels.cycles.json +++ b/src/data/method/pt/labels.cycles.json @@ -20,7 +20,7 @@ "cycle.station.api-publishing": "Publicação da API", "cycle.station.monitoring-and-improving": "Monitorizacao e melhoria da API", "cycle.station.integration-capability-strategy": "Estratégia da capacidade de integração", - "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer & Provider Commitments", + "cycle.station.integration-consumer-requirements-onboarding": "Compromissos do consumidor e fornecedor de integração", "cycle.station.integration-architecture-decision": "Arquitetura de integracao e decisoes de plataforma", "cycle.station.integration-solution-design": "Conceção da solução de integração", "cycle.station.integration-delivery-operations": "Entrega e operações da integração", @@ -47,7 +47,7 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitorize a saúde da API, a adoção, os resultados dos consumidores, a fiabilidade e as oportunidades de melhoria após a disponibilização.", "cycle.automation-cycle.title": "Ciclo de Automação", "cycle.automation-cycle.description": "Um ciclo para selecionar, desenhar, entregar, ativar e melhorar soluções de automação envolvendo pessoas, regras, fluxos de trabalho, agentes, integrações, automação de interface e operações.", - "cycle.automation-cycle.purpose": "Guide teams from external customer and capability outcomes to a validated, governed, and operable automation solution.", + "cycle.automation-cycle.purpose": "Orientar as equipas desde os resultados do cliente externo e da capacidade até uma solução de automação validada, governada e operável.", "cycle.audience.automation-owners": "Responsáveis pela automação", "cycle.audience.process-owners": "Responsáveis pelo processo", "cycle.audience.automation-teams": "Equipas de automação", @@ -57,33 +57,33 @@ "cycle.station.automation-readiness-review": "Revisão de prontidão da automação", "cycle.station.automation-enablement": "Rollout e enablement da automação", "cycle.station.automation-monitoring-improvement": "Monitorização e melhoria da automação", - "cycle.automation-cycle.station.api-product-strategy.description": "Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.", - "cycle.automation-cycle.station.api-consumer-experience.description": "Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.", - "cycle.automation-cycle.station.api-platform-architecture.description": "Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.", - "cycle.automation-cycle.station.api-design.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.", - "cycle.automation-cycle.station.api-delivery.description": "Build, configure, test, version, deploy, and prepare the operating model for the selected automation path, including ownership, environments, runbooks, monitoring, fallback, rollback, support, and known risks.", + "cycle.automation-cycle.station.api-product-strategy.description": "Comece pelo cliente externo mais significativo. Reutilize evidência da jornada e do valor da capacidade para validar se uma hipótese de automação deve avançar.", + "cycle.automation-cycle.station.api-consumer-experience.description": "Clarifique os requisitos de processo, experiência, domínio, serviço e não funcionais que o workflow e a arquitetura posteriores devem satisfazer.", + "cycle.automation-cycle.station.api-platform-architecture.description": "Use impacto, localização, capacidade e requisitos anteriores para escolher a abordagem de implementação da automação e registar a justificação e os riscos restantes.", + "cycle.automation-cycle.station.api-design.description": "Desenhe o workflow interno necessário para entregar os resultados selecionados para o cliente e a capacidade, incluindo alocação de trabalho, controlos, exceções, recuperação, evidência e monitorização.", + "cycle.automation-cycle.station.api-delivery.description": "Construa, configure, teste, versione, implante e prepare o modelo operacional para o caminho de automação selecionado, incluindo propriedade, ambientes, runbooks, monitorização, fallback, rollback, suporte e riscos conhecidos.", "cycle.automation-cycle.station.api-audit.description": "Use uma checklist de prontidão para rever evidências e registar a decisão de lançamento: pronto, pronto com condições, correção necessária ou não aprovado.", "cycle.automation-cycle.station.api-publishing.description": "Ative e implemente a automação com segurança usando comunicação, formação, instruções operacionais, caminhos de suporte, monitorização da adoção, canais de feedback, rollout faseado, pausa e condições de rollback.", - "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor actual automation outcomes, run success and failure, exceptions, retries, interventions, cycle time, waiting time, cost, errors, unsafe actions, adoption, trust, realized benefit, and which hypothesis assumptions were supported or rejected.", - "cycle.station.process-user-automation-requirements": "Process & Experience Requirements", - "cycle.station.automation-architecture-platform-decision": "Automation Architecture & Platform Decision", - "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.", - "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.", + "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitorize os resultados reais da automação, sucessos e falhas de execução, exceções, repetições, intervenções, tempo de ciclo, tempo de espera, custo, erros, ações inseguras, adoção, confiança, benefício realizado e quais hipóteses foram confirmadas ou rejeitadas.", + "cycle.station.process-user-automation-requirements": "Requisitos de processo e experiência", + "cycle.station.automation-architecture-platform-decision": "Decisão de arquitetura e plataforma de automação", + "cycle.integration-productization-cycle.station.integration-capability-strategy.description": "Comece pela jornada do cliente, pelo valor da capacidade e pela evidência de viabilidade; depois valide se a capacidade de integração reutilizável proposta deve avançar.", + "cycle.integration-productization-cycle.station.integration-consumer-requirements-onboarding.description": "Acorde compromissos de fornecedor e consumidor para acesso, validação, serviço, tratamento de falhas, recuperação, compatibilidade e ciclo de vida.", "cycle.integration-productization-cycle.station.integration-architecture-platform-decisions.description": "Selecionar arquitetura de integração, estilo de implementação e capacidades de plataforma considerando restrições e governação.", "cycle.integration-productization-cycle.station.integration-solution-design.description": "Desenhar a solução de integração, contratos, esquemas, estruturas de dados, mapeamentos e padrões de interação ou entrega para o estilo selecionado.", "cycle.integration-productization-cycle.station.integration-delivery-operations.description": "Construir, testar, fazer deployment e operar a capacidade de integração usando o estilo selecionado e contrato validado.", "cycle.integration-productization-cycle.station.integration-readiness-assurance.description": "Garantir prontidão, governação, qualidade, segurança, compliance e evidências operacionais da integração antes do lançamento.", "cycle.integration-productization-cycle.station.integration-publishing-enablement.description": "Publicar a capacidade de integração para que equipas possam descobri-la, avaliá-la, pedir acesso, completar onboarding, reutilizá-la e obter suporte.", "cycle.integration-productization-cycle.station.integration-monitoring-improvement.description": "Monitorizar fiabilidade, reutilização, incidentes, desempenho, resultados dos consumidores e necessidades de melhoria da integração.", - "cycle.station.consumer-producer-service-requirements": "Consumer & Producer Commitments", + "cycle.station.consumer-producer-service-requirements": "Compromissos do consumidor e produtor", "cycle.station.capability-architecture-platform-decisions": "Decisões de arquitetura e plataforma da capacidade", "cycle.station.capability-solution-interaction-design": "Desenho da solução e interação da capacidade", "cycle.station.capability-delivery-operations": "Entrega e operações da capacidade", "cycle.station.capability-readiness-assurance": "Garantia de prontidão da capacidade", "cycle.station.capability-publishing-enablement": "Publicação e enablement da capacidade", "cycle.station.capability-monitoring-improvement": "Monitorização e melhoria da capacidade", - "cycle.capability-productization-cycle.station.capability-strategy.description": "Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.", - "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.", + "cycle.capability-productization-cycle.station.capability-strategy.description": "Comece pela jornada do cliente, pelo valor da capacidade e pela evidência de viabilidade; depois valide se a capacidade digital reutilizável proposta deve avançar.", + "cycle.capability-productization-cycle.station.capability-consumer-producer-requirements.description": "Acorde compromissos mútuos entre proprietário, produtor e consumidor para acesso, serviço, suporte, mudança e ciclo de vida.", "cycle.capability-productization-cycle.station.capability-architecture-platform-decisions.description": "Decisões de arquitetura e plataforma da capacidade: Guia a definição da capacidade reutilizável desde a hipótese e requisitos de consumidor/produtor até arquitetura, desenho da solução, entrega, prontidão, publicação e melhoria contínua.", "cycle.capability-productization-cycle.station.capability-solution-interaction-design.description": "Desenho da solução e interação da capacidade: Guia a definição da capacidade reutilizável desde a hipótese e requisitos de consumidor/produtor até arquitetura, desenho da solução, entrega, prontidão, publicação e melhoria contínua.", "cycle.capability-productization-cycle.station.capability-delivery-operations.description": "Entrega e operações da capacidade: Guia a definição da capacidade reutilizável desde a hipótese e requisitos de consumidor/produtor até arquitetura, desenho da solução, entrega, prontidão, publicação e melhoria contínua.", diff --git a/src/data/method/pt/labels.resources.json b/src/data/method/pt/labels.resources.json index c69827a..8dd60c6 100644 --- a/src/data/method/pt/labels.resources.json +++ b/src/data/method/pt/labels.resources.json @@ -133,9 +133,9 @@ "resource.contract-first-design.outcomes": "Melhor compreensão dos princípios de conceção da primeira fase do contrato", "resource.contract-first-design.outcomes.1": "Abordagem normalizada utilizando a conceção orientada por contrato", "resource.contract-first-design.outcomes.2": "Melhoria da implementação das práticas de API relacionadas", - "resource.contract-first-design.steps": "Apply contract-first or design-first approaches to validate integration contracts before implementation.", - "resource.contract-first-design.steps.1": "Define interface contracts, schemas, responsibilities, usage rules, examples, and lifecycle expectations.", - "resource.contract-first-design.steps.2": "Use machine-readable formats such as OpenAPI, AsyncAPI, event schemas, message schemas, file schemas, data contracts, or interface specifications where possible.", + "resource.contract-first-design.steps": "Aplique abordagens contract-first ou design-first para validar contratos de integração antes da implementação.", + "resource.contract-first-design.steps.1": "Defina contratos de interface, esquemas, responsabilidades, regras de utilização, exemplos e expectativas de ciclo de vida.", + "resource.contract-first-design.steps.2": "Use formatos legíveis por máquina sempre que possível, como OpenAPI, AsyncAPI, esquemas de eventos, esquemas de mensagens, esquemas de ficheiros, contratos de dados ou especificações de interface.", "resource.contract-first-design.tips": "Personalize a conceção do Contract First ao seu domínio", "resource.contract-first-design.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas", "resource.cross-functional-collaboration-best-practices.title": "Boas práticas de colaboração interfuncional", @@ -296,47 +296,47 @@ "resource.api-value-proposition-canvas.tips.1": "Destaque para as características que aliviam as dores ou aumentam os ganhos", "resource.api-value-proposition-canvas.tips.2": "Validar as características com os utilizadores da API para garantir o alinhamento", "resource.business-impact-canvas.title": "Canvas de Impacto no Negócio", - "resource.business-impact-canvas.description": "Assess expected benefits, operational, customer, employee, financial, compliance, strategic, risk, and not-proceeding impacts that should shape prioritization and decisions.", - "resource.business-impact-canvas.outcomes": "Documented business impact assessment", - "resource.business-impact-canvas.outcomes.1": "Expected value, affected groups, financial and strategic consequences, risks, and mitigations clarified", + "resource.business-impact-canvas.description": "Avalie benefícios esperados e impactos operacionais, de cliente, colaborador, financeiros, de conformidade, estratégicos, de risco e de não avançar que devem orientar a priorização e as decisões.", + "resource.business-impact-canvas.outcomes": "Avaliação documentada do impacto de negócio", + "resource.business-impact-canvas.outcomes.1": "Valor esperado, grupos afetados, consequências financeiras e estratégicas, riscos e mitigações clarificados", "resource.business-impact-canvas.outcomes.2": "Evidências para decisões de oportunidade, arquitetura, rollout, prontidão e avançar ou parar", - "resource.business-impact-canvas.steps": "Identify expected business, customer, employee, quality, speed, risk, compliance, and strategic benefits.", - "resource.business-impact-canvas.steps.1": "Assess operational efficiency, customer and employee impact, financial impact, compliance impact, strategic impact, and impact of not proceeding.", + "resource.business-impact-canvas.steps": "Identifique benefícios esperados de negócio, cliente, colaborador, qualidade, velocidade, risco, conformidade e estratégia.", + "resource.business-impact-canvas.steps.1": "Avalie a eficiência operacional, o impacto no cliente e nos colaboradores, o impacto financeiro, o impacto de conformidade, o impacto estratégico e o impacto de não avançar.", "resource.business-impact-canvas.steps.2": "Identifique riscos, criticidade, mitigações, riscos residuais e consequências da decisão.", "resource.business-impact-canvas.steps.3": "Use as evidências de impacto para orientar priorização, arquitetura, rollout, prontidão e decisões de avançar ou parar.", "resource.business-impact-canvas.steps.4": "Riscos dos dados: Identificar os riscos para a exatidão ou disponibilidade dos dados.", "resource.business-impact-canvas.steps.5": "Formas de mitigar os riscos dos dados: Planear estratégias para lidar com os riscos dos dados.", - "resource.business-impact-canvas.tips": "Use this for value and consequence evidence, not only risk and resilience analysis.", - "resource.business-impact-canvas.tips.1": "Include business stakeholders, users or employees, operations, compliance, and technical stakeholders.", - "resource.business-impact-canvas.tips.2": "Record the impact of not proceeding as well as expected benefits.", + "resource.business-impact-canvas.tips": "Use isto como evidência de valor e consequências, não apenas para análise de risco e resiliência.", + "resource.business-impact-canvas.tips.1": "Inclua partes interessadas de negócio, utilizadores ou colaboradores, operações, conformidade e partes interessadas técnicas.", + "resource.business-impact-canvas.tips.2": "Registe o impacto de não avançar, bem como os benefícios esperados.", "resource.capacity-canvas.title": "Canvas de Capacidade", - "resource.capacity-canvas.description": "Quantify demand, load, timing, availability, and scaling needs for capabilities, automations, integrations, or services.", + "resource.capacity-canvas.description": "Quantifique procura, carga, temporização, disponibilidade e necessidades de escala para capacidades, automações, integrações ou serviços.", "resource.capacity-canvas.outcomes": "Alinhamento da capacidade da API com os volumes de negócios", "resource.capacity-canvas.outcomes.1": "Preparado para as futuras tendências de consumo", "resource.capacity-canvas.outcomes.2": "Estratégias definidas de armazenamento em cache e limitação de taxa", - "resource.capacity-canvas.steps": "Current Business Volumes: Quantify current business volumes and transaction rates.", - "resource.capacity-canvas.steps.1": "Future Consumption Trends: Estimate future demand and growth assumptions.", - "resource.capacity-canvas.steps.2": "Peak Load and Availability Requirements: Quantify peak load and availability needs.", - "resource.capacity-canvas.steps.3": "Caching, rate limiting, and scaling approaches: Record architecture follow-up options where capacity requires them.", + "resource.capacity-canvas.steps": "Volumes de negócio atuais: quantifique os volumes de negócio atuais e as taxas de transação.", + "resource.capacity-canvas.steps.1": "Tendências futuras de consumo: estime a procura futura e as hipóteses de crescimento.", + "resource.capacity-canvas.steps.2": "Requisitos de pico de carga e disponibilidade: quantifique o pico de carga e as necessidades de disponibilidade.", + "resource.capacity-canvas.steps.3": "Cache, limitação de taxa e abordagens de escala: registe opções de seguimento de arquitetura quando a capacidade as exigir.", "resource.capacity-canvas.steps.4": "Propor estratégias de escalonamento", - "resource.capacity-canvas.tips": "Use requirements canvases to capture what users need; use this canvas to quantify demand and inform scaling decisions.", + "resource.capacity-canvas.tips": "Use canvases de requisitos para captar o que os utilizadores precisam; use este canvas para quantificar a procura e informar decisões de escala.", "resource.capacity-canvas.tips.1": "Definir cenários de picos de utilização", "resource.capacity-canvas.tips.2": "Incluir testes de escalabilidade na fase de planeamento", - "resource.customer-journey-canvas.title": "Customer Journey Canvas", - "resource.customer-journey-canvas.description": "What journey does the most external meaningful customer experience, and what should improve?", - "resource.customer-journey-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.customer-journey-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.customer-journey-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.customer-journey-canvas.steps": "Start with the most external meaningful customer. Describe their real journey before tracing inward to capabilities, internal processes, or implementation choices.", - "resource.customer-journey-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.customer-journey-canvas.steps.2": "Carry the resulting decisions forward to the next station.", + "resource.customer-journey-canvas.title": "Canvas da Jornada do Cliente", + "resource.customer-journey-canvas.description": "Que jornada vive o cliente externo mais significativo, e o que deve melhorar?", + "resource.customer-journey-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.customer-journey-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.customer-journey-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.customer-journey-canvas.steps": "Comece pelo cliente externo mais significativo. Descreva a sua jornada real antes de avançar para dentro, para capacidades, processos internos ou escolhas de implementação.", + "resource.customer-journey-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.customer-journey-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", "resource.customer-journey-canvas.steps.3": "Mapear as etapas do percurso com entradas/saídas", "resource.customer-journey-canvas.steps.4": "Identificar os problemas dos clientes", "resource.customer-journey-canvas.steps.5": "Resumir os ganhos dos clientes", "resource.customer-journey-canvas.steps.6": "Definir os inputs necessários e os outputs resultantes", "resource.customer-journey-canvas.steps.7": "Definir interações API para cada etapa", - "resource.customer-journey-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.customer-journey-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.customer-journey-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.customer-journey-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", "resource.event-canvas.title": "Canvas de Eventos", "resource.event-canvas.description": "Conceber APIs orientadas para eventos, definindo eventos, accionadores e lógica de processamento.", "resource.event-canvas.outcomes": "Arquitetura orientada para eventos definida", @@ -519,9 +519,9 @@ "resource.automation-readiness-checklist.outcomes": "Decisão de prontidão da automação", "resource.automation-readiness-checklist.outcomes.1": "Decisão de lançamento registada como pronto, pronto com condições, correção necessária ou não aprovado", "resource.automation-readiness-checklist.outcomes.2": "Evidências, achados bloqueantes, riscos residuais, condições, ações de correção, responsável pela decisão e data da decisão documentados antes do lançamento", - "resource.automation-readiness-checklist.steps": "Review completed operating model, workflow design, business rules, controls, access, data handling, exception paths, and evidence.", + "resource.automation-readiness-checklist.steps": "Revise o modelo operacional concluído, o desenho do workflow, as regras de negócio, os controlos, o acesso, o tratamento de dados, os caminhos de exceção e a evidência.", "resource.automation-readiness-checklist.steps.1": "Identifique achados bloqueantes, riscos residuais aceites, evidências em falta e ações de correção necessárias.", - "resource.automation-readiness-checklist.steps.2": "Record the release decision, decision owner, decision date, conditions, and follow-up actions.", + "resource.automation-readiness-checklist.steps.2": "Registe a decisão de lançamento, o responsável pela decisão, a data da decisão, as condições e as ações de seguimento.", "resource.automation-readiness-checklist.steps.3": "Registe lacunas por resolver, decisões e riscos aceites antes da publicação.", "resource.automation-readiness-checklist.tips": "Utilize antes da publicação e novamente após alterações materiais ao workflow ou às regras.", "resource.automation-readiness-checklist.tips.1": "Torne explícitas nas evidências a supervisão humana e a gestão de exceções.", @@ -542,107 +542,107 @@ "resource.api-testing-best-practices.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.", "resource.apiops-CI-CD-for-apis.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.", "resource.api-audit-checklist.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.", - "resource.automation-opportunity-canvas.title": "Automation Hypothesis & Validation Canvas", - "resource.automation-opportunity-canvas.description": "Turn existing journey, value, impact, domain, and capacity evidence into a testable automation decision.", - "resource.automation-opportunity-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-opportunity-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-opportunity-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-opportunity-canvas.steps": "Reuse earlier canvas outputs. Record only the remaining hypothesis, uncertainties, validation, and decision.", - "resource.automation-opportunity-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-opportunity-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-opportunity-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-opportunity-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-workflow-canvas.title": "Automation Workflow Canvas", - "resource.automation-workflow-canvas.description": "Design the internal workflow needed to deliver the selected customer and capability outcomes.", - "resource.automation-workflow-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-workflow-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-workflow-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-workflow-canvas.steps": "Reuse customer journey, value proposition, domain, and validation evidence. Define the internal work, allocate it between people and automation, and add only execution details.", - "resource.automation-workflow-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-workflow-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-workflow-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-workflow-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-architecture-decision-canvas.title": "Automation Architecture Decision Canvas", - "resource.automation-architecture-decision-canvas.description": "Choose the implementation approach using evidence already gathered.", - "resource.automation-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-architecture-decision-canvas.steps": "Bring forward constraints and responsibility choices. Compare only viable mechanisms, then record the decision and remaining risks.", - "resource.automation-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.automation-readiness-operations-canvas.title": "Automation Readiness & Operations Canvas", - "resource.automation-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before readiness review.", - "resource.automation-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.automation-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.automation-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.automation-readiness-operations-canvas.steps": "Reuse design decisions. Record ownership, operational arrangements, evidence, recovery, and remaining readiness gaps.", - "resource.automation-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.automation-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.automation-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.automation-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.user-operator-experience-requirements.title": "User and Operator Experience Requirements", - "resource.user-operator-experience-requirements.description": "A cycle-specific view of experience, operational, and non-functional requirements for automation users, operators, approvers, and support teams.", - "resource.user-operator-experience-requirements.outcomes": "User and operator expectations clarified", - "resource.user-operator-experience-requirements.outcomes.1": "Availability, timeliness, permissions, support, recovery, observability, and activation needs captured", - "resource.user-operator-experience-requirements.outcomes.2": "Constraints ready for later architecture, workflow, and capacity decisions", - "resource.user-operator-experience-requirements.steps": "Capture user, operator, approver, and support goals for the target process.", - "resource.user-operator-experience-requirements.steps.1": "Clarify availability, timeliness, volume, data quality, permissions, activation, changes, support, observability, recovery, and continuity expectations.", - "resource.user-operator-experience-requirements.steps.2": "Translate the expectations into constraints for later automation design without choosing the implementation mechanism.", - "resource.user-operator-experience-requirements.tips": "Use this label in the Automation Cycle instead of API consumer wording.", - "resource.user-operator-experience-requirements.tips.1": "Keep the shared underlying requirements canvas intact for other cycles.", - "resource.automation-monitoring-value-metrics.title": "Automation Monitoring and Value Metrics", + "resource.automation-opportunity-canvas.title": "Canvas de hipótese e validação de automação", + "resource.automation-opportunity-canvas.description": "Transforme evidência existente de jornada, valor, impacto, domínio e capacidade numa decisão de automação testável.", + "resource.automation-opportunity-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.automation-opportunity-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.automation-opportunity-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.automation-opportunity-canvas.steps": "Reutilize resultados de canvases anteriores. Registe apenas a hipótese restante, incertezas, validação e decisão.", + "resource.automation-opportunity-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.automation-opportunity-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.automation-opportunity-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.automation-opportunity-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.automation-workflow-canvas.title": "Canvas de workflow de automação", + "resource.automation-workflow-canvas.description": "Desenhe o workflow interno necessário para entregar os resultados selecionados para o cliente e a capacidade.", + "resource.automation-workflow-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.automation-workflow-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.automation-workflow-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.automation-workflow-canvas.steps": "Reutilize evidência da jornada do cliente, proposta de valor, domínio e validação. Defina o trabalho interno, distribua-o entre pessoas e automação e acrescente apenas detalhes de execução.", + "resource.automation-workflow-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.automation-workflow-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.automation-workflow-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.automation-workflow-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.automation-architecture-decision-canvas.title": "Canvas de decisão de arquitetura de automação", + "resource.automation-architecture-decision-canvas.description": "Escolha a abordagem de implementação usando a evidência já recolhida.", + "resource.automation-architecture-decision-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.automation-architecture-decision-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.automation-architecture-decision-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.automation-architecture-decision-canvas.steps": "Traga restrições e escolhas de responsabilidade. Compare apenas mecanismos viáveis e depois registe a decisão e os riscos restantes.", + "resource.automation-architecture-decision-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.automation-architecture-decision-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.automation-architecture-decision-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.automation-architecture-decision-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.automation-readiness-operations-canvas.title": "Canvas de prontidão e operações de automação", + "resource.automation-readiness-operations-canvas.description": "Prepare a evidência operacional mínima necessária antes da revisão de prontidão.", + "resource.automation-readiness-operations-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.automation-readiness-operations-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.automation-readiness-operations-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.automation-readiness-operations-canvas.steps": "Reutilize decisões de desenho. Registe propriedade, acordos operacionais, evidência, recuperação e lacunas de prontidão restantes.", + "resource.automation-readiness-operations-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.automation-readiness-operations-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.automation-readiness-operations-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.automation-readiness-operations-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.user-operator-experience-requirements.title": "Requisitos de experiência do utilizador e operador", + "resource.user-operator-experience-requirements.description": "Uma visão específica do ciclo sobre requisitos de experiência, operacionais e não funcionais para utilizadores, operadores, aprovadores e equipas de suporte da automação.", + "resource.user-operator-experience-requirements.outcomes": "Expectativas de utilizadores e operadores clarificadas", + "resource.user-operator-experience-requirements.outcomes.1": "Necessidades de disponibilidade, pontualidade, permissões, suporte, recuperação, observabilidade e ativação captadas", + "resource.user-operator-experience-requirements.outcomes.2": "Restrições prontas para decisões posteriores de arquitetura, workflow e capacidade", + "resource.user-operator-experience-requirements.steps": "Capte objetivos de utilizadores, operadores, aprovadores e suporte para o processo-alvo.", + "resource.user-operator-experience-requirements.steps.1": "Clarifique expectativas de disponibilidade, pontualidade, volume, qualidade dos dados, permissões, ativação, mudanças, suporte, observabilidade, recuperação e continuidade.", + "resource.user-operator-experience-requirements.steps.2": "Traduza as expectativas em restrições para o desenho posterior da automação sem escolher o mecanismo de implementação.", + "resource.user-operator-experience-requirements.tips": "Use este rótulo no Ciclo de Automação em vez da terminologia de consumidor de API.", + "resource.user-operator-experience-requirements.tips.1": "Mantenha intacto o canvas de requisitos subjacente partilhado para outros ciclos.", + "resource.automation-monitoring-value-metrics.title": "Monitorização da automação e métricas de valor", "resource.automation-monitoring-value-metrics.description": "Guia para medir resultados, desempenho operacional, comportamento do utilizador, risco, recuperação, valor realizado, aprendizagem da hipótese e decisões de ciclo de vida após o rollout.", - "resource.automation-monitoring-value-metrics.outcomes": "Automation monitoring, value, and learning evidence", - "resource.automation-monitoring-value-metrics.outcomes.1": "Actual outcomes, run success, failure, exception, retry, intervention, processing time, waiting time, correction, incident, adoption, and benefit signals reviewed", - "resource.automation-monitoring-value-metrics.outcomes.2": "Automation Hypothesis assumptions reviewed and improvement, expansion, redesign, or retirement decisions prioritized", - "resource.automation-monitoring-value-metrics.steps": "Outcomes and value: compare expected process, user, and business outcomes with actual evidence.", - "resource.automation-monitoring-value-metrics.steps.1": "Operational performance: review successful runs, failures, partial completions, exceptions, retries, timeouts, interventions, processing time, waiting time, and cost.", - "resource.automation-monitoring-value-metrics.steps.2": "User, risk, and recovery signals: review errors, corrections, unsafe actions, bypassing, mistrust, support needs, fallback events, and recovery failures.", - "resource.automation-monitoring-value-metrics.steps.3": "Learning and lifecycle decision: decide which hypothesis assumptions were supported or rejected and whether to improve, expand, restrict, redesign, pause, retire, or add backlog items.", + "resource.automation-monitoring-value-metrics.outcomes": "Evidência de monitorização, valor e aprendizagem da automação", + "resource.automation-monitoring-value-metrics.outcomes.1": "Resultados reais, sucessos de execução, falhas, exceções, repetições, intervenções, tempo de processamento, tempo de espera, correções, incidentes, adoção e sinais de benefício revistos", + "resource.automation-monitoring-value-metrics.outcomes.2": "Hipóteses da automação revistas e decisões de melhoria, expansão, redesenho ou descontinuação priorizadas", + "resource.automation-monitoring-value-metrics.steps": "Resultados e valor: compare resultados esperados de processo, utilizador e negócio com evidência real.", + "resource.automation-monitoring-value-metrics.steps.1": "Desempenho operacional: reveja execuções bem-sucedidas, falhas, conclusões parciais, exceções, repetições, timeouts, intervenções, tempo de processamento, tempo de espera e custo.", + "resource.automation-monitoring-value-metrics.steps.2": "Sinais de utilizador, risco e recuperação: reveja erros, correções, ações inseguras, contornos, desconfiança, necessidades de suporte, eventos de fallback e falhas de recuperação.", + "resource.automation-monitoring-value-metrics.steps.3": "Aprendizagem e decisão de ciclo de vida: decida que hipóteses foram confirmadas ou rejeitadas e se deve melhorar, expandir, restringir, redesenhar, pausar, descontinuar ou adicionar itens ao backlog.", "resource.automation-monitoring-value-metrics.tips": "A monitorização transforma evidências operacionais, de utilizador, risco e valor em decisões de ciclo de vida e num backlog de melhoria.", - "resource.automation-monitoring-value-metrics.tips.1": "Include signals that show adoption, trust, human oversight needs, recovery needs, and realized value.", - "resource.integration-capability-hypothesis-canvas.title": "Integration Capability Validation Canvas", - "resource.integration-capability-hypothesis-canvas.description": "Validate whether a proposed reusable integration capability should proceed.", - "resource.integration-capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-capability-hypothesis-canvas.steps": "Reuse journey, value, domain, business model, impact, and capacity evidence instead of restating it.", - "resource.integration-capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-consumer-provider-requirements-canvas.title": "Integration Consumer & Provider Commitments Canvas", - "resource.integration-consumer-provider-requirements-canvas.description": "Agree the responsibilities needed to use and provide a reusable integration capability.", - "resource.integration-consumer-provider-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-consumer-provider-requirements-canvas.steps": "Bring forward consumers, use cases, service needs, and constraints. Record commitments rather than rediscovering requirements.", - "resource.integration-consumer-provider-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-consumer-provider-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-consumer-provider-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-architecture-decision-canvas.title": "Integration Architecture Decision Canvas", - "resource.integration-architecture-decision-canvas.description": "Choose the integration style and platform using evidence already gathered.", - "resource.integration-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-architecture-decision-canvas.steps": "Bring forward consumer commitments, impact, location, and capacity. Compare only viable styles and record the decision.", - "resource.integration-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.integration-readiness-operations-canvas.title": "Integration Readiness & Operations Canvas", - "resource.integration-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before integration readiness review.", - "resource.integration-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-readiness-operations-canvas.steps": "Reuse contracts and design decisions. Record ownership, operations, evidence, recovery, and remaining readiness gaps.", - "resource.integration-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.automation-monitoring-value-metrics.tips.1": "Inclua sinais que mostram adoção, confiança, necessidades de supervisão humana, necessidades de recuperação e valor realizado.", + "resource.integration-capability-hypothesis-canvas.title": "Canvas de validação da capacidade de integração", + "resource.integration-capability-hypothesis-canvas.description": "Valide se uma capacidade de integração reutilizável proposta deve avançar.", + "resource.integration-capability-hypothesis-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.integration-capability-hypothesis-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.integration-capability-hypothesis-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.integration-capability-hypothesis-canvas.steps": "Reutilize evidência de jornada, valor, domínio, modelo de negócio, impacto e capacidade em vez de a repetir.", + "resource.integration-capability-hypothesis-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.integration-capability-hypothesis-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.integration-capability-hypothesis-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.integration-capability-hypothesis-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.integration-consumer-provider-requirements-canvas.title": "Canvas de compromissos do consumidor e fornecedor de integração", + "resource.integration-consumer-provider-requirements-canvas.description": "Acorde as responsabilidades necessárias para usar e fornecer uma capacidade de integração reutilizável.", + "resource.integration-consumer-provider-requirements-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.integration-consumer-provider-requirements-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.integration-consumer-provider-requirements-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.integration-consumer-provider-requirements-canvas.steps": "Traga consumidores, casos de uso, necessidades de serviço e restrições. Registe compromissos em vez de redescobrir requisitos.", + "resource.integration-consumer-provider-requirements-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.integration-consumer-provider-requirements-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.integration-consumer-provider-requirements-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.integration-consumer-provider-requirements-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.integration-architecture-decision-canvas.title": "Canvas de decisão de arquitetura de integração", + "resource.integration-architecture-decision-canvas.description": "Escolha o estilo de integração e a plataforma usando evidência já recolhida.", + "resource.integration-architecture-decision-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.integration-architecture-decision-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.integration-architecture-decision-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.integration-architecture-decision-canvas.steps": "Traga compromissos dos consumidores, impacto, localização e capacidade. Compare apenas estilos viáveis e registe a decisão.", + "resource.integration-architecture-decision-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.integration-architecture-decision-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.integration-architecture-decision-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.integration-architecture-decision-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.integration-readiness-operations-canvas.title": "Canvas de prontidão e operações de integração", + "resource.integration-readiness-operations-canvas.description": "Prepare a evidência operacional mínima necessária antes da revisão de prontidão da integração.", + "resource.integration-readiness-operations-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.integration-readiness-operations-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.integration-readiness-operations-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.integration-readiness-operations-canvas.steps": "Reutilize contratos e decisões de desenho. Registe propriedade, operações, evidência, recuperação e lacunas de prontidão restantes.", + "resource.integration-readiness-operations-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.integration-readiness-operations-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.integration-readiness-operations-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.integration-readiness-operations-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", "resource.integration-consumer-onboarding-guide.title": "Guia de onboarding de consumidores de integração", "resource.integration-consumer-onboarding-guide.description": "Guia de onboarding de consumidores de integração apoia o planeamento, decisão, entrega, publicação ou melhoria de uma capacidade de integração reutilizável.", "resource.integration-consumer-onboarding-guide.outcomes": "Base de trabalho de integração documentada", @@ -813,66 +813,66 @@ "resource.integration-lifecycle-management-guide.steps.2": "Use os resultados no desenho, entrega, prontidão, publicação ou melhoria.", "resource.integration-lifecycle-management-guide.tips": "Adapte este recurso ao estilo de integração escolhido.", "resource.integration-lifecycle-management-guide.tips.1": "Inclua produtores, consumidores, plataforma, operações, segurança, compliance e negócio.", - "resource.integration-solution-design-canvas.title": "Integration Solution Design Canvas", - "resource.integration-solution-design-canvas.description": "Refine the selected architecture into an implementable integration design.", - "resource.integration-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.integration-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.integration-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.integration-solution-design-canvas.steps": "Reuse the selected style, domain concepts, interaction needs, and commitments. Add only implementation-specific design.", - "resource.integration-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.integration-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.integration-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.integration-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-hypothesis-canvas.title": "Capability Validation Canvas", - "resource.capability-hypothesis-canvas.description": "Validate whether a proposed reusable digital capability should proceed.", - "resource.capability-hypothesis-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-hypothesis-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-hypothesis-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-hypothesis-canvas.steps": "Reuse journey, value proposition, business model, impact, domain, and capacity outputs instead of repeating them.", - "resource.capability-hypothesis-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-hypothesis-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-hypothesis-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-hypothesis-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-consumer-producer-requirements-canvas.title": "Capability Consumer & Producer Commitments Canvas", - "resource.capability-consumer-producer-requirements-canvas.description": "Agree mutual commitments for providing and consuming a reusable capability.", - "resource.capability-consumer-producer-requirements-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-consumer-producer-requirements-canvas.steps": "Reuse consumers, value, channels, service needs, and ownership from earlier canvases. Capture only agreed commitments and gaps.", - "resource.capability-consumer-producer-requirements-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-consumer-producer-requirements-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-consumer-producer-requirements-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-architecture-decision-canvas.title": "Capability Architecture Decision Canvas", - "resource.capability-architecture-decision-canvas.description": "Choose how the capability will be delivered using evidence already gathered.", - "resource.capability-architecture-decision-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-architecture-decision-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-architecture-decision-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-architecture-decision-canvas.steps": "Bring forward value, commitments, impact, location, capacity, and domain decisions. Compare only viable implementation styles.", - "resource.capability-architecture-decision-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-architecture-decision-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-architecture-decision-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-architecture-decision-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-solution-design-canvas.title": "Capability Solution Design Canvas", - "resource.capability-solution-design-canvas.description": "Refine the selected implementation style into a clear consumer-facing capability design.", - "resource.capability-solution-design-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-solution-design-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-solution-design-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-solution-design-canvas.steps": "Reuse value, domain, interaction, commitments, and architecture outputs. Add only solution-specific design.", - "resource.capability-solution-design-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-solution-design-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-solution-design-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-solution-design-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", - "resource.capability-readiness-operations-canvas.title": "Capability Readiness & Operations Canvas", - "resource.capability-readiness-operations-canvas.description": "Prepare the minimum operating evidence needed before capability readiness review.", - "resource.capability-readiness-operations-canvas.outcomes": "A focused decision or design artifact that reuses earlier evidence", - "resource.capability-readiness-operations-canvas.outcomes.1": "Earlier canvas outputs are referenced instead of repeated", - "resource.capability-readiness-operations-canvas.outcomes.2": "The next decision, design step, or readiness gap is explicit", - "resource.capability-readiness-operations-canvas.steps": "Reuse business model, commitments, and solution design. Record only operational ownership, evidence, continuity, and readiness gaps.", - "resource.capability-readiness-operations-canvas.steps.1": "Complete only the sections that add a new decision or refinement.", - "resource.capability-readiness-operations-canvas.steps.2": "Carry the resulting decisions forward to the next station.", - "resource.capability-readiness-operations-canvas.tips": "Link to earlier canvases rather than copying their content.", - "resource.capability-readiness-operations-canvas.tips.1": "Use supporting canvases only when the required evidence does not already exist.", + "resource.integration-solution-design-canvas.title": "Canvas de desenho da solução de integração", + "resource.integration-solution-design-canvas.description": "Refine a arquitetura selecionada num desenho de integração implementável.", + "resource.integration-solution-design-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.integration-solution-design-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.integration-solution-design-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.integration-solution-design-canvas.steps": "Reutilize o estilo selecionado, conceitos de domínio, necessidades de interação e compromissos. Acrescente apenas desenho específico da implementação.", + "resource.integration-solution-design-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.integration-solution-design-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.integration-solution-design-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.integration-solution-design-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.capability-hypothesis-canvas.title": "Canvas de validação da capacidade", + "resource.capability-hypothesis-canvas.description": "Valide se uma capacidade digital reutilizável proposta deve avançar.", + "resource.capability-hypothesis-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.capability-hypothesis-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.capability-hypothesis-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.capability-hypothesis-canvas.steps": "Reutilize resultados de jornada, proposta de valor, modelo de negócio, impacto, domínio e capacidade em vez de os repetir.", + "resource.capability-hypothesis-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.capability-hypothesis-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.capability-hypothesis-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.capability-hypothesis-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.capability-consumer-producer-requirements-canvas.title": "Canvas de compromissos do consumidor e produtor da capacidade", + "resource.capability-consumer-producer-requirements-canvas.description": "Acorde compromissos mútuos para fornecer e consumir uma capacidade reutilizável.", + "resource.capability-consumer-producer-requirements-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.capability-consumer-producer-requirements-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.capability-consumer-producer-requirements-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.capability-consumer-producer-requirements-canvas.steps": "Reutilize consumidores, valor, canais, necessidades de serviço e propriedade de canvases anteriores. Capte apenas compromissos acordados e lacunas.", + "resource.capability-consumer-producer-requirements-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.capability-consumer-producer-requirements-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.capability-consumer-producer-requirements-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.capability-consumer-producer-requirements-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.capability-architecture-decision-canvas.title": "Canvas de decisão de arquitetura da capacidade", + "resource.capability-architecture-decision-canvas.description": "Escolha como a capacidade será entregue usando evidência já recolhida.", + "resource.capability-architecture-decision-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.capability-architecture-decision-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.capability-architecture-decision-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.capability-architecture-decision-canvas.steps": "Traga valor, compromissos, impacto, localização, capacidade e decisões de domínio. Compare apenas estilos de implementação viáveis.", + "resource.capability-architecture-decision-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.capability-architecture-decision-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.capability-architecture-decision-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.capability-architecture-decision-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.capability-solution-design-canvas.title": "Canvas de desenho da solução da capacidade", + "resource.capability-solution-design-canvas.description": "Refine o estilo de implementação selecionado num desenho de capacidade claro para o consumidor.", + "resource.capability-solution-design-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.capability-solution-design-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.capability-solution-design-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.capability-solution-design-canvas.steps": "Reutilize resultados de valor, domínio, interação, compromissos e arquitetura. Acrescente apenas desenho específico da solução.", + "resource.capability-solution-design-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.capability-solution-design-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.capability-solution-design-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.capability-solution-design-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", + "resource.capability-readiness-operations-canvas.title": "Canvas de prontidão e operações da capacidade", + "resource.capability-readiness-operations-canvas.description": "Prepare a evidência operacional mínima necessária antes da revisão de prontidão da capacidade.", + "resource.capability-readiness-operations-canvas.outcomes": "Um artefacto de decisão ou desenho focado que reutiliza evidência anterior", + "resource.capability-readiness-operations-canvas.outcomes.1": "Os resultados de canvases anteriores são referenciados em vez de repetidos", + "resource.capability-readiness-operations-canvas.outcomes.2": "A próxima decisão, passo de desenho ou lacuna de prontidão está explícita", + "resource.capability-readiness-operations-canvas.steps": "Reutilize modelo de negócio, compromissos e desenho da solução. Registe apenas propriedade operacional, evidência, continuidade e lacunas de prontidão.", + "resource.capability-readiness-operations-canvas.steps.1": "Preencha apenas as secções que acrescentam uma nova decisão ou refinamento.", + "resource.capability-readiness-operations-canvas.steps.2": "Leve as decisões resultantes para a próxima estação.", + "resource.capability-readiness-operations-canvas.tips": "Ligue aos canvases anteriores em vez de copiar o seu conteúdo.", + "resource.capability-readiness-operations-canvas.tips.1": "Use canvases de apoio apenas quando a evidência necessária ainda não existir.", "resource.capability-consumer-onboarding-guide.title": "Guia de onboarding de consumidores da capacidade", "resource.capability-consumer-onboarding-guide.description": "Guia de onboarding de consumidores da capacidade apoia a etapa de capacidade correspondente com decisões, evidências, responsabilidades, riscos e próximos passos específicos.", "resource.capability-consumer-onboarding-guide.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", diff --git a/src/data/method/pt/labels.stations.json b/src/data/method/pt/labels.stations.json index e91a3d3..3bd6f71 100644 --- a/src/data/method/pt/labels.stations.json +++ b/src/data/method/pt/labels.stations.json @@ -67,33 +67,33 @@ "station.api-audit.title": "Auditoria de API - Auditoria de APIs para conformidade e qualidade", "station.api-audit.description": "Rever a prontidão para lançamento usando evidências de desenho, testes, operações, permissões, monitorização, suporte, fallback, rollback, risco e ownership antes do uso em produção.", "station.api-audit.why_it_matters": "Uma decisão formal de prontidão impede que soluções de automação sejam lançadas sem evidências claras, riscos aceites, ações de remediação e ownership de negócio e operacional.", - "station.api-audit.apply_in_work": "", + "station.api-audit.apply_in_work": "Use a evidência de prontidão para tomar uma decisão explícita de avançar, avançar com condições ou não avançar antes do uso em produção.", "station.api-audit.outcomes": "Decisão formal de prontidão", "station.api-audit.outcomes.1": "Evidências, achados bloqueantes, riscos residuais aceites e ações de correção revistos", "station.api-audit.outcomes.2": "Decisão de lançamento registada como pronto, pronto com condições, correção necessária ou não aprovado", - "station.api-audit.outcomes.3": "Business and operational ownership confirmed before release", + "station.api-audit.outcomes.3": "Propriedade de negócio e operacional confirmada antes do lançamento", "station.api-audit.how_it_works": "Rever o desenho concluído, evidências de teste, modelo operacional, permissões, credenciais, monitorização, suporte, fallback e rollback.", "station.api-audit.how_it_works.1": "Verificar se riscos conhecidos, exceções, ações inseguras, supervisão humana, requisitos de conformidade e suposições não resolvidas foram tratados ou explicitamente aceites.", "station.api-audit.how_it_works.2": "Registar achados bloqueantes, riscos residuais aceites, condições de lançamento e ações de remediação necessárias.", "station.api-publishing.title": "Publicação de API - Publique APIs com confiança", "station.api-publishing.description": "Habilitar soluções lançadas para que utilizadores, operadores, equipas afetadas, sistemas consumidores, consumidores de serviço e equipas de suporte as adotem com segurança.", "station.api-publishing.why_it_matters": "Soluções de automação só criam valor após rollout quando as pessoas afetadas e sistemas consumidores entendem o que muda, como acesso e operação funcionam, onde obter suporte e quando o rollout deve pausar, expandir ou reverter.", - "station.api-publishing.apply_in_work": "", + "station.api-publishing.apply_in_work": "Planeie rollout, enablement, suporte, feedback e rollback para que as soluções lançadas possam ser adotadas com segurança.", "station.api-publishing.outcomes": "Plano seguro de rollout e enablement", "station.api-publishing.outcomes.1": "Pessoas afetadas, responsabilidades alteradas, decisões, handoffs e práticas de trabalho compreendidos", "station.api-publishing.outcomes.2": "Ativação, acesso, permissões, abordagem de rollout, enablement e suporte preparados", - "station.api-publishing.outcomes.3": "Feedback, adoption, trust, issue handling, pause, rollback, manual operation, and expansion controls defined", + "station.api-publishing.outcomes.3": "Feedback, adoção, confiança, tratamento de problemas, pausa, rollback, operação manual e controlos de expansão definidos", "station.api-publishing.how_it_works": "Pessoas afetadas e trabalho alterado: quem vai usar, operar, suportar, aprovar, consumir ou ser afetado pelo lançamento, e que responsabilidades, decisões, handoffs ou práticas de trabalho vão mudar?", "station.api-publishing.how_it_works.1": "Ativação e abordagem de rollout: como serão geridos acesso, permissões, piloto, rollout faseado, grupos restritos, operação paralela e expansão?", "station.api-publishing.how_it_works.2": "Enablement e suporte: que comunicação, formação, instruções operacionais e caminhos de suporte são necessários?", "station.monitoring-and-improving.title": "Monitorização e melhoria - para valor API", - "station.monitoring-and-improving.description": "Monitor actual outcomes, operational performance, user behavior, risk, recovery, realized value, and improvement opportunities after release.", + "station.monitoring-and-improving.description": "Monitorize resultados reais, desempenho operacional, comportamento dos utilizadores, risco, recuperação, valor realizado e oportunidades de melhoria após o lançamento.", "station.monitoring-and-improving.why_it_matters": "Soluções lançadas precisam de evidências para mostrar se os resultados esperados estão a ser alcançados, onde ainda é necessária intervenção manual ou recuperação, e qual decisão de ciclo de vida deve ser tomada a seguir.", - "station.monitoring-and-improving.apply_in_work": "", - "station.monitoring-and-improving.outcomes": "Measured outcome, performance, risk, recovery, and value evidence", - "station.monitoring-and-improving.outcomes.1": "Expected outcomes, run performance, user behavior, risks, support needs, and realized value reviewed", - "station.monitoring-and-improving.outcomes.2": "Hypothesis assumptions and lifecycle options assessed", - "station.monitoring-and-improving.outcomes.3": "Improvement backlog informed by operational, user, risk, and value evidence", + "station.monitoring-and-improving.apply_in_work": "Use evidência operacional, de utilizador, risco e valor para decidir o que melhorar, expandir, restringir, pausar ou retirar.", + "station.monitoring-and-improving.outcomes": "Evidência medida de resultado, desempenho, risco, recuperação e valor", + "station.monitoring-and-improving.outcomes.1": "Resultados esperados, desempenho de execução, comportamento dos utilizadores, riscos, necessidades de suporte e valor realizado revistos", + "station.monitoring-and-improving.outcomes.2": "Hipóteses e opções de ciclo de vida avaliadas", + "station.monitoring-and-improving.outcomes.3": "Backlog de melhorias informado por evidência operacional, de utilizador, risco e valor", "station.monitoring-and-improving.how_it_works": "Resultados e valor: os resultados esperados de processo, utilizador e negócio estão a ser alcançados?", "station.monitoring-and-improving.how_it_works.1": "Desempenho operacional: o que mostram execuções bem-sucedidas, falhas, conclusões parciais, exceções, retries, timeouts, intervenções, tempo de processamento, tempo de espera e custo?", "station.monitoring-and-improving.how_it_works.2": "Sinais de utilizador, risco e recuperação: que erros, correções, ações inseguras, contornos, desconfiança, necessidades de suporte, eventos de fallback ou falhas de recuperação ocorrem?", @@ -464,297 +464,9 @@ "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Monitorizar as métricas de desempenho (por exemplo, chamadas APIs, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).", "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analisar as métricas de utilização da API e incorporar o feedback dos utilizadores nas iterações da API.", "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Crie o hábito de analisar os indicadores e planear actividades de melhoria contínua.", - "cycle.capability-productization-cycle.station.api-product-strategy.title": "Estratégia", - "cycle.capability-productization-cycle.station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor, os consumidores, a propriedade e os objetivos de negócio da capacidade.", - "cycle.capability-productization-cycle.station.api-product-strategy.why_it_matters": "O trabalho de integração e API salta muitas vezes demasiado cedo para um padrão técnico. Esta estação mantém a equipa focada na jornada de negócio, no significado do domínio, no valor, no potencial de reutilização, na propriedade e na viabilidade antes de selecionar APIs, eventos, ficheiros, streams, produtos de dados ou integração direta.", - "cycle.capability-productization-cycle.station.api-product-strategy.apply_in_work": "Utilize canvases partilhados de jornada, domínio, proposta de valor e modelo de negócio para recolher requisitos independentes da tecnologia e decidir se a capacidade deve ser reutilizável.", - "cycle.capability-productization-cycle.station.api-product-strategy.outcomes": "Uma declaração de oportunidade de capacidade independente da tecnologia", - "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.1": "Compreensão partilhada dos consumidores, produtores, conceitos de domínio e potencial de reutilização", - "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.2": "Uma proposta de valor e um modelo de negócio da capacidade antes da seleção da arquitetura", - "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works": "Mapeie a jornada do cliente ou parceiro que cria a necessidade da capacidade e revela tarefas, dores, ganhos, entradas, saídas e pontos de decisão.", - "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.1": "Defina as entidades principais, atributos, relações, propriedade e regras de negócio que a capacidade deve respeitar.", - "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.2": "Utilize o Canvas da Proposta de Valor da Capacidade para captar tarefas, ganhos, dores e funcionalidades reutilizáveis da capacidade para os consumidores, sem nomear a tecnologia de disponibilização demasiado cedo.", - "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.3": "Utilize o Canvas do Modelo de Negócio da Capacidade para clarificar propriedade, parceiros, canais, custos, benefícios, suporte e expectativas de ciclo de vida da capacidade reutilizável.", - "cycle.capability-productization-cycle.station.api-consumer-experience.title": "Requisitos e integração de consumidores", - "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Recolha requisitos de integração dos consumidores, normas, requisitos não funcionais, expectativas de serviço, restrições, necessidades de segurança, protocolos permitidos, atualidade dos dados, SLAs, observabilidade, recuperação, requisitos de adoção e responsabilidades dos produtores.", - "cycle.capability-productization-cycle.station.api-consumer-experience.why_it_matters": "A arquitetura certa depende dos objetivos dos consumidores, das expectativas de integração, dos níveis de serviço, das necessidades de qualidade dos dados, da tolerância à mudança, da observabilidade, do suporte e das restrições dos produtores.", - "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works": "Utilize o Canvas de Requisitos da Experiência do Consumidor para captar objetivos dos consumidores, disponibilidade, atualidade, volume, desempenho, qualidade dos dados, segurança, integração, mudança, observabilidade e expectativas de recuperação.", - "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.1": "Utilize orientação de integração para descrever como os consumidores vão encontrar, solicitar, testar, obter aprovação e começar a utilizar a capacidade.", - "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.2": "Utilize a jornada e os requisitos resultantes para melhorar a integração, a documentação, o suporte e os ciclos de feedback dos consumidores da capacidade.", - "cycle.capability-productization-cycle.station.api-consumer-experience.apply_in_work": "Utilize orientação de experiência e integração de consumidores para tornar explícitas as expectativas de consumidores e produtores.", - "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes": "Requisitos dos consumidores e expectativas de integração documentados", - "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.1": "Responsabilidades dos produtores e expectativas de suporte claras", - "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.2": "Restrições relevantes para a arquitetura prontas para apoiar decisões", - "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.3": "Adoção melhorada através de empatia com os consumidores, normas e clareza dos produtores", - "cycle.capability-productization-cycle.station.api-platform-architecture.title": "Decisões de arquitetura e plataforma", - "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Utilize requisitos e restrições para decidir o padrão de arquitetura certo e as capacidades de plataforma de suporte.", - "cycle.capability-productization-cycle.station.api-platform-architecture.why_it_matters": "As escolhas de arquitetura devem resultar de evidências sobre impacto de negócio, localizações, fronteiras de confiança, capacidade, latência, propriedade dos dados, consistência, operabilidade, segurança, privacidade, governação e custo.", - "cycle.capability-productization-cycle.station.api-platform-architecture.apply_in_work": "Compare estilos de arquitetura viáveis com os requisitos recolhidos e documente o padrão selecionado e a respetiva justificação.", - "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes": "Uma escolha de arquitetura justificada", - "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.1": "Riscos, localizações, capacidade, segurança, privacidade e restrições de operabilidade documentados", - "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.2": "Justificação clara para API, evento, ficheiro, stream, produto de dados, integração direta ou disponibilização híbrida", - "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works": "Utilize o Canvas de Impacto no Negócio para identificar riscos de disponibilidade, segurança e dados que influenciam as opções de arquitetura.", - "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.1": "Utilize o Canvas de Localizações para captar restrições geopolíticas, regulamentares, de rede, residência e fronteiras de confiança.", - "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.2": "Utilize o Canvas de Capacidade para captar volumes atuais e futuros, picos, latência, cache, limitação de pedidos e expectativas de escala.", - "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.3": "Utilize orientação de métricas e análise para definir como a capacidade escolhida será monitorizada e melhorada.", - "cycle.capability-productization-cycle.station.api-design.title": "Conceção da solução e da interface", - "cycle.capability-productization-cycle.station.api-design.description": "Conceba o contrato de interface e o modelo de interação para o estilo de disponibilização selecionado.", - "cycle.capability-productization-cycle.station.api-design.why_it_matters": "Depois de conhecido o padrão de arquitetura, a conceção deve transformar os requisitos da capacidade em contratos de interface, interações, esquemas, regras de dados, expectativas de ciclo de vida e obrigações dos consumidores claros.", - "cycle.capability-productization-cycle.station.api-design.apply_in_work": "Selecione os recursos de conceção adequados ao estilo de disponibilização escolhido e documente o contrato de interface antes da implementação.", - "cycle.capability-productization-cycle.station.api-design.outcomes": "Um contrato de interface validado para o estilo de disponibilização selecionado", - "cycle.capability-productization-cycle.station.api-design.outcomes.1": "Decisões consistentes sobre interação, dados, eventos, ficheiros, fluxos de trabalho ou contratos de API", - "cycle.capability-productization-cycle.station.api-design.outcomes.2": "Rastreabilidade da conceção até aos requisitos da capacidade e dos consumidores", - "cycle.capability-productization-cycle.station.api-design.outcomes.3": "Conceções alinhadas com modelos de domínio e padrões de interação", - "cycle.capability-productization-cycle.station.api-design.how_it_works": "Reutilize o Canvas de Domínio para confirmar objetos de negócio, termos, regras e propriedade antes da conceção do contrato.", - "cycle.capability-productization-cycle.station.api-design.how_it_works.1": "Utilize o Canvas de Interação para descrever como consumidores, sistemas ou utilizadores interagem com a capacidade.", - "cycle.capability-productization-cycle.station.api-design.how_it_works.2": "Utilize recursos de conceção REST quando a interface selecionada for uma API REST.", - "cycle.capability-productization-cycle.station.api-design.how_it_works.3": "Utilize recursos de Canvas de Eventos quando a interface selecionada for orientada por eventos.", - "cycle.capability-productization-cycle.station.api-design.how_it_works.4": "Utilize recursos de conceção GraphQL quando a interface selecionada for GraphQL.", - "cycle.capability-productization-cycle.station.api-design.how_it_works.5": "Utilize os princípios de conceção e a orientação de estilo para alinhar decisões de conceção com regras partilhadas e permitir validação de auditoria consistente.", - "cycle.capability-productization-cycle.station.api-design.how_it_works.6": "Aplique abordagens contract-first ou design-first para captar e validar o contrato de interface antes da implementação.", - "cycle.capability-productization-cycle.station.api-design.how_it_works.7": "Utilize a lista de verificação de auditoria para garantir que a conceção cumpre requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.", - "cycle.capability-productization-cycle.station.api-delivery.title": "Entrega e operações", - "cycle.capability-productization-cycle.station.api-delivery.description": "Construa, teste, disponibilize e opere a capacidade usando o estilo de disponibilização selecionado e o contrato de interface validado.", - "cycle.capability-productization-cycle.station.api-delivery.why_it_matters": "Uma capacidade reutilizável precisa de entrega e operações fiáveis, quer se torne uma API, stream de eventos, troca de ficheiros, produto de dados ou integração direta.", - "cycle.capability-productization-cycle.station.api-delivery.apply_in_work": "Aplique orientação de entrega, testes, CI/CD, operações e segurança ao estilo de disponibilização escolhido.", - "cycle.capability-productization-cycle.station.api-delivery.outcomes": "Uma capacidade entregue e alinhada com o contrato de interface validado", - "cycle.capability-productization-cycle.station.api-delivery.outcomes.1": "Testes, disponibilização e controlos de ambiente automatizados", - "cycle.capability-productization-cycle.station.api-delivery.outcomes.2": "Práticas de segurança, operações e qualidade adequadas ao padrão escolhido", - "cycle.capability-productization-cycle.station.api-delivery.outcomes.3": "Controlos de entrega e disponibilização rastreáveis", - "cycle.capability-productization-cycle.station.api-delivery.how_it_works": "Utilize boas práticas de desenvolvimento para implementar o contrato de interface validado com frameworks, bibliotecas e normas da equipa estabelecidos.", - "cycle.capability-productization-cycle.station.api-delivery.how_it_works.1": "Construa a implementação a partir do contrato de interface validado, usando frameworks, bibliotecas e normas da equipa estabelecidos.", - "cycle.capability-productization-cycle.station.api-delivery.how_it_works.2": "Utilize orientação de testes para verificar funcionalidade, qualidade dos dados, compatibilidade, segurança, desempenho, resiliência e expectativas de recuperação.", - "cycle.capability-productization-cycle.station.api-delivery.how_it_works.3": "Utilize orientação de CI/CD para automatizar construção, testes, disponibilização, configuração e rastreabilidade.", - "cycle.capability-productization-cycle.station.api-delivery.how_it_works.4": "Utilize orientação de segurança para proteger dados, acesso, credenciais e fronteiras da plataforma.", - "cycle.capability-productization-cycle.station.api-delivery.how_it_works.5": "Utilize a lista de verificação de auditoria para garantir que a solução cumpre requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.", - "cycle.capability-productization-cycle.station.api-audit.title": "Garantia de qualidade e prontidão", - "cycle.capability-productization-cycle.station.api-audit.description": "Audite o contrato de interface, os controlos, o modelo de suporte, a observabilidade, a documentação e a prontidão de ciclo de vida da capacidade antes da disponibilização.", - "cycle.capability-productization-cycle.station.api-audit.why_it_matters": "As capacidades reutilizáveis criam riscos operacionais, de dados, segurança, privacidade, conformidade e impacto nos consumidores. As verificações de prontidão reduzem surpresas antes da publicação ou utilização em produção.", - "cycle.capability-productization-cycle.station.api-audit.apply_in_work": "Utilize recursos de auditoria e conformidade para verificar que a capacidade está pronta para disponibilização controlada e reutilização.", - "cycle.capability-productization-cycle.station.api-audit.outcomes": "Prontidão para disponibilização e reutilização documentada", - "cycle.capability-productization-cycle.station.api-audit.outcomes.1": "Lacunas e mitigações conhecidas antes da publicação", - "cycle.capability-productization-cycle.station.api-audit.outcomes.2": "Evidências para aprovação de governação, conformidade, suporte e operações", - "cycle.capability-productization-cycle.station.api-audit.outcomes.3": "Risco reduzido de problemas em produção", - "cycle.capability-productization-cycle.station.api-audit.how_it_works": "Utilize a lista de verificação de auditoria como checklist de qualidade reutilizável para contrato de interface, documentação, segurança, desempenho e prontidão de conformidade.", - "cycle.capability-productization-cycle.station.api-audit.how_it_works.1": "Utilize checklists, linters e ferramentas de teste para verificar consistência e conformidade com normas.", - "cycle.capability-productization-cycle.station.api-audit.how_it_works.2": "Colabore com equipas de governação e especialistas de domínio para garantir que a capacidade está pronta para produção.", - "cycle.capability-productization-cycle.station.api-publishing.title": "Publicação e capacitação", - "cycle.capability-productization-cycle.station.api-publishing.description": "Publique informação sobre a capacidade reutilizável para que os consumidores a possam descobrir, solicitar, integrar, utilizar e obter suporte.", - "cycle.capability-productization-cycle.station.api-publishing.why_it_matters": "As capacidades reutilizáveis só criam valor quando os consumidores as conseguem encontrar, compreender o respetivo contrato de interface e expectativas de serviço, solicitar acesso e saber quem é responsável pelo suporte e pelas decisões de ciclo de vida.", - "cycle.capability-productization-cycle.station.api-publishing.apply_in_work": "Publique propriedade, documentação, integração, contactos de suporte, expectativas de serviço, estado de ciclo de vida e caminhos para pedidos de acesso.", - "cycle.capability-productization-cycle.station.api-publishing.outcomes": "Uma capacidade reutilizável detetável", - "cycle.capability-productization-cycle.station.api-publishing.outcomes.1": "Expectativas claras de integração, acesso, suporte e serviço", - "cycle.capability-productization-cycle.station.api-publishing.outcomes.2": "Informação de ciclo de vida e propriedade disponível para consumidores e equipas de governação", - "cycle.capability-productization-cycle.station.api-publishing.outcomes.3": "Consumidores capacitados para utilizar e reutilizar a capacidade", - "cycle.capability-productization-cycle.station.api-publishing.how_it_works": "Publique informação sobre a capacidade nos catálogos, portais, gateways ou ambientes adequados para apoiar a reutilização por vários consumidores.", - "cycle.capability-productization-cycle.station.api-publishing.how_it_works.1": "Documente como os consumidores encontram e utilizam a capacidade, incluindo processos de integração e registo.", - "cycle.capability-productization-cycle.station.api-publishing.how_it_works.2": "Garanta que os modelos de segurança, a configuração de acesso e os termos legais são claros e acessíveis aos consumidores.", - "cycle.capability-productization-cycle.station.monitoring-and-improving.title": "Monitorização e melhoria", - "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitorize a utilização, fiabilidade, qualidade dos dados, resultados dos consumidores, custo operacional e oportunidades de reutilização após a disponibilização.", - "cycle.capability-productization-cycle.station.monitoring-and-improving.why_it_matters": "As capacidades precisam de feedback contínuo para permanecerem fiáveis, valiosas, rentáveis e reutilizáveis à medida que consumidores, sistemas, dados e plataformas mudam.", - "cycle.capability-productization-cycle.station.monitoring-and-improving.apply_in_work": "Utilize práticas de métricas, análise e envolvimento para melhorar a capacidade ao longo do tempo.", - "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes": "Saúde e valor da capacidade medidos", - "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.1": "Backlog de melhorias informado por feedback operacional e dos consumidores", - "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.2": "Sinais de reutilização, fiabilidade, qualidade dos dados e custo disponíveis para os responsáveis", - "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.3": "Melhoria contínua alinhada com as necessidades dos consumidores", - "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works": "Utilize orientação de métricas e análise para definir medidas de utilização da capacidade, fiabilidade, qualidade dos dados, custo, adoção e valor para os consumidores.", - "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analise métricas de utilização e incorpore feedback dos consumidores nas iterações da capacidade.", - "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Estabeleça o hábito de rever métricas e planear atividades de melhoria contínua.", "station.api-audit.how_it_works.3": "Decidir se o lançamento está pronto, pronto com condições, requer remediação ou não é aprovado.", "station.api-audit.how_it_works.4": "Registar o owner da decisão, a data da decisão e as evidências usadas.", "station.api-audit.how_it_works.5": "Confirmar que nada avança para lançamento sem ownership de negócio e operacional claro.", "station.api-publishing.how_it_works.3": "Feedback e controlo: como serão monitorizados adoção, confiança, uso real, problemas e comportamento inesperado, e que condições acionam pausa, rollback ou retorno à operação manual?", - "station.monitoring-and-improving.how_it_works.3": "Aprendizagem e decisão de ciclo de vida: que suposições da hipótese foram suportadas ou rejeitadas, e a solução deve ser melhorada, expandida, restringida, redesenhada, pausada ou retirada?", - "station.integration-capability-strategy.title": "Estratégia de capacidade de integração", - "station.integration-capability-strategy.description": "Estratégia de capacidade de integração clarifica as próximas decisões, evidências, responsabilidades e riscos para uma capacidade de integração reutilizável. Use canvases de apoio apenas quando as evidências necessárias ainda não existirem.", - "station.integration-capability-strategy.why_it_matters": "O trabalho de integração mantém-se consistente quando consumidores, produtores, plataforma, operações, segurança, compliance e negócio usam as mesmas evidências e decisões.", - "station.integration-capability-strategy.apply_in_work": "Use os recursos de integração específicos da estação como base de trabalho principal.", - "station.integration-capability-strategy.outcomes": "Decisão ou base de trabalho de integração documentada", - "station.integration-capability-strategy.outcomes.1": "Responsabilidades, evidências e restrições relevantes clarificadas", - "station.integration-capability-strategy.outcomes.2": "Riscos, pressupostos e próximos passos visíveis", - "station.integration-capability-strategy.outcomes.3": "Resultados preparados para a estação seguinte", - "station.integration-capability-strategy.how_it_works": "Clarifique objetivo, escopo, consumidores, produtores e contexto de plataforma.", - "station.integration-capability-strategy.how_it_works.1": "Documente evidências, decisões, riscos e responsabilidades relevantes.", - "station.integration-capability-strategy.how_it_works.2": "Verifique dependências com arquitetura, desenho, operações, publicação e monitorização.", - "station.integration-capability-strategy.how_it_works.3": "Registe pontos em aberto e próximos passos.", - "station.integration-consumer-requirements-onboarding.title": "Requisitos de consumidores e onboarding de integração", - "station.integration-consumer-requirements-onboarding.description": "Requisitos de consumidores e onboarding de integração clarifica as próximas decisões, evidências, responsabilidades e riscos para uma capacidade de integração reutilizável.", - "station.integration-consumer-requirements-onboarding.why_it_matters": "O trabalho de integração mantém-se consistente quando consumidores, produtores, plataforma, operações, segurança, compliance e negócio usam as mesmas evidências e decisões.", - "station.integration-consumer-requirements-onboarding.apply_in_work": "Use os recursos de integração específicos da estação como base de trabalho principal.", - "station.integration-consumer-requirements-onboarding.outcomes": "Decisão ou base de trabalho de integração documentada", - "station.integration-consumer-requirements-onboarding.outcomes.1": "Responsabilidades, evidências e restrições relevantes clarificadas", - "station.integration-consumer-requirements-onboarding.outcomes.2": "Riscos, pressupostos e próximos passos visíveis", - "station.integration-consumer-requirements-onboarding.outcomes.3": "Resultados preparados para a estação seguinte", - "station.integration-consumer-requirements-onboarding.how_it_works": "Clarifique objetivo, escopo, consumidores, produtores e contexto de plataforma.", - "station.integration-consumer-requirements-onboarding.how_it_works.1": "Documente evidências, decisões, riscos e responsabilidades relevantes.", - "station.integration-consumer-requirements-onboarding.how_it_works.2": "Verifique dependências com arquitetura, desenho, operações, publicação e monitorização.", - "station.integration-consumer-requirements-onboarding.how_it_works.3": "Registe pontos em aberto e próximos passos.", - "station.integration-architecture-platform-decisions.title": "Decisões de arquitetura e plataforma de integração", - "station.integration-architecture-platform-decisions.description": "Decisões de arquitetura e plataforma de integração clarifica as próximas decisões, evidências, responsabilidades e riscos para uma capacidade de integração reutilizável.", - "station.integration-architecture-platform-decisions.why_it_matters": "O trabalho de integração mantém-se consistente quando consumidores, produtores, plataforma, operações, segurança, compliance e negócio usam as mesmas evidências e decisões.", - "station.integration-architecture-platform-decisions.apply_in_work": "Use os recursos de integração específicos da estação como base de trabalho principal.", - "station.integration-architecture-platform-decisions.outcomes": "Decisão ou base de trabalho de integração documentada", - "station.integration-architecture-platform-decisions.outcomes.1": "Responsabilidades, evidências e restrições relevantes clarificadas", - "station.integration-architecture-platform-decisions.outcomes.2": "Riscos, pressupostos e próximos passos visíveis", - "station.integration-architecture-platform-decisions.outcomes.3": "Resultados preparados para a estação seguinte", - "station.integration-architecture-platform-decisions.how_it_works": "Clarifique objetivo, escopo, consumidores, produtores e contexto de plataforma.", - "station.integration-architecture-platform-decisions.how_it_works.1": "Documente evidências, decisões, riscos e responsabilidades relevantes.", - "station.integration-architecture-platform-decisions.how_it_works.2": "Verifique dependências com arquitetura, desenho, operações, publicação e monitorização.", - "station.integration-architecture-platform-decisions.how_it_works.3": "Registe pontos em aberto e próximos passos.", - "station.integration-solution-design.title": "Desenho da solução de integração", - "station.integration-solution-design.description": "Desenho da solução de integração clarifica as próximas decisões, evidências, responsabilidades e riscos para uma capacidade de integração reutilizável.", - "station.integration-solution-design.why_it_matters": "O trabalho de integração mantém-se consistente quando consumidores, produtores, plataforma, operações, segurança, compliance e negócio usam as mesmas evidências e decisões.", - "station.integration-solution-design.apply_in_work": "Use os recursos de integração específicos da estação como base de trabalho principal.", - "station.integration-solution-design.outcomes": "Decisão ou base de trabalho de integração documentada", - "station.integration-solution-design.outcomes.1": "Responsabilidades, evidências e restrições relevantes clarificadas", - "station.integration-solution-design.outcomes.2": "Riscos, pressupostos e próximos passos visíveis", - "station.integration-solution-design.outcomes.3": "Resultados preparados para a estação seguinte", - "station.integration-solution-design.how_it_works": "Clarifique objetivo, escopo, consumidores, produtores e contexto de plataforma.", - "station.integration-solution-design.how_it_works.1": "Documente evidências, decisões, riscos e responsabilidades relevantes.", - "station.integration-solution-design.how_it_works.2": "Verifique dependências com arquitetura, desenho, operações, publicação e monitorização.", - "station.integration-solution-design.how_it_works.3": "Registe pontos em aberto e próximos passos.", - "station.integration-delivery-operations.title": "Entrega e operações de integração", - "station.integration-delivery-operations.description": "Entrega e operações de integração clarifica as próximas decisões, evidências, responsabilidades e riscos para uma capacidade de integração reutilizável.", - "station.integration-delivery-operations.why_it_matters": "O trabalho de integração mantém-se consistente quando consumidores, produtores, plataforma, operações, segurança, compliance e negócio usam as mesmas evidências e decisões.", - "station.integration-delivery-operations.apply_in_work": "Use os recursos de integração específicos da estação como base de trabalho principal.", - "station.integration-delivery-operations.outcomes": "Decisão ou base de trabalho de integração documentada", - "station.integration-delivery-operations.outcomes.1": "Responsabilidades, evidências e restrições relevantes clarificadas", - "station.integration-delivery-operations.outcomes.2": "Riscos, pressupostos e próximos passos visíveis", - "station.integration-delivery-operations.outcomes.3": "Resultados preparados para a estação seguinte", - "station.integration-delivery-operations.how_it_works": "Clarifique objetivo, escopo, consumidores, produtores e contexto de plataforma.", - "station.integration-delivery-operations.how_it_works.1": "Documente evidências, decisões, riscos e responsabilidades relevantes.", - "station.integration-delivery-operations.how_it_works.2": "Verifique dependências com arquitetura, desenho, operações, publicação e monitorização.", - "station.integration-delivery-operations.how_it_works.3": "Registe pontos em aberto e próximos passos.", - "station.integration-readiness-assurance.title": "Garantia de prontidão da integração", - "station.integration-readiness-assurance.description": "Garantia de prontidão da integração clarifica as próximas decisões, evidências, responsabilidades e riscos para uma capacidade de integração reutilizável.", - "station.integration-readiness-assurance.why_it_matters": "O trabalho de integração mantém-se consistente quando consumidores, produtores, plataforma, operações, segurança, compliance e negócio usam as mesmas evidências e decisões.", - "station.integration-readiness-assurance.apply_in_work": "Use os recursos de integração específicos da estação como base de trabalho principal.", - "station.integration-readiness-assurance.outcomes": "Decisão ou base de trabalho de integração documentada", - "station.integration-readiness-assurance.outcomes.1": "Responsabilidades, evidências e restrições relevantes clarificadas", - "station.integration-readiness-assurance.outcomes.2": "Riscos, pressupostos e próximos passos visíveis", - "station.integration-readiness-assurance.outcomes.3": "Resultados preparados para a estação seguinte", - "station.integration-readiness-assurance.how_it_works": "Clarifique objetivo, escopo, consumidores, produtores e contexto de plataforma.", - "station.integration-readiness-assurance.how_it_works.1": "Documente evidências, decisões, riscos e responsabilidades relevantes.", - "station.integration-readiness-assurance.how_it_works.2": "Verifique dependências com arquitetura, desenho, operações, publicação e monitorização.", - "station.integration-readiness-assurance.how_it_works.3": "Registe pontos em aberto e próximos passos.", - "station.integration-publishing-enablement.title": "Publicação e enablement da integração", - "station.integration-publishing-enablement.description": "Publicação e enablement da integração clarifica as próximas decisões, evidências, responsabilidades e riscos para uma capacidade de integração reutilizável.", - "station.integration-publishing-enablement.why_it_matters": "O trabalho de integração mantém-se consistente quando consumidores, produtores, plataforma, operações, segurança, compliance e negócio usam as mesmas evidências e decisões.", - "station.integration-publishing-enablement.apply_in_work": "Use os recursos de integração específicos da estação como base de trabalho principal.", - "station.integration-publishing-enablement.outcomes": "Decisão ou base de trabalho de integração documentada", - "station.integration-publishing-enablement.outcomes.1": "Responsabilidades, evidências e restrições relevantes clarificadas", - "station.integration-publishing-enablement.outcomes.2": "Riscos, pressupostos e próximos passos visíveis", - "station.integration-publishing-enablement.outcomes.3": "Resultados preparados para a estação seguinte", - "station.integration-publishing-enablement.how_it_works": "Clarifique objetivo, escopo, consumidores, produtores e contexto de plataforma.", - "station.integration-publishing-enablement.how_it_works.1": "Documente evidências, decisões, riscos e responsabilidades relevantes.", - "station.integration-publishing-enablement.how_it_works.2": "Verifique dependências com arquitetura, desenho, operações, publicação e monitorização.", - "station.integration-publishing-enablement.how_it_works.3": "Registe pontos em aberto e próximos passos.", - "station.integration-monitoring-improvement.title": "Monitorização e melhoria da integração", - "station.integration-monitoring-improvement.description": "Monitorização e melhoria da integração clarifica as próximas decisões, evidências, responsabilidades e riscos para uma capacidade de integração reutilizável.", - "station.integration-monitoring-improvement.why_it_matters": "O trabalho de integração mantém-se consistente quando consumidores, produtores, plataforma, operações, segurança, compliance e negócio usam as mesmas evidências e decisões.", - "station.integration-monitoring-improvement.apply_in_work": "Use os recursos de integração específicos da estação como base de trabalho principal.", - "station.integration-monitoring-improvement.outcomes": "Decisão ou base de trabalho de integração documentada", - "station.integration-monitoring-improvement.outcomes.1": "Responsabilidades, evidências e restrições relevantes clarificadas", - "station.integration-monitoring-improvement.outcomes.2": "Riscos, pressupostos e próximos passos visíveis", - "station.integration-monitoring-improvement.outcomes.3": "Resultados preparados para a estação seguinte", - "station.integration-monitoring-improvement.how_it_works": "Clarifique objetivo, escopo, consumidores, produtores e contexto de plataforma.", - "station.integration-monitoring-improvement.how_it_works.1": "Documente evidências, decisões, riscos e responsabilidades relevantes.", - "station.integration-monitoring-improvement.how_it_works.2": "Verifique dependências com arquitetura, desenho, operações, publicação e monitorização.", - "station.integration-monitoring-improvement.how_it_works.3": "Registe pontos em aberto e próximos passos.", - "station.capability-strategy.title": "Estratégia de capacidade", - "station.capability-strategy.description": "Estratégia de capacidade clarifica a capacidade, consumidores, produtores, expectativas de serviço, riscos, evidências e próximas decisões ao nível reutilizável.", - "station.capability-strategy.why_it_matters": "O Capability Cycle permanece acima do estilo de implementação e só referencia detalhes de API, integração, workflow, produto de dados ou aplicação após a decisão de estilo.", - "station.capability-strategy.apply_in_work": "", - "station.capability-strategy.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "station.capability-strategy.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "station.capability-strategy.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "station.capability-strategy.outcomes.3": "Resultados preparados para a estação seguinte", - "station.capability-strategy.how_it_works": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "station.capability-strategy.how_it_works.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "station.capability-strategy.how_it_works.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "station.capability-strategy.how_it_works.3": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "station.capability-consumer-producer-requirements.title": "Requisitos de consumidor, produtor e serviço", - "station.capability-consumer-producer-requirements.description": "Requisitos de consumidor, produtor e serviço clarifica a capacidade, consumidores, produtores, expectativas de serviço, riscos, evidências e próximas decisões ao nível reutilizável.", - "station.capability-consumer-producer-requirements.why_it_matters": "O Capability Cycle permanece acima do estilo de implementação e só referencia detalhes de API, integração, workflow, produto de dados ou aplicação após a decisão de estilo.", - "station.capability-consumer-producer-requirements.apply_in_work": "", - "station.capability-consumer-producer-requirements.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "station.capability-consumer-producer-requirements.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "station.capability-consumer-producer-requirements.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "station.capability-consumer-producer-requirements.outcomes.3": "Resultados preparados para a estação seguinte", - "station.capability-consumer-producer-requirements.how_it_works": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "station.capability-consumer-producer-requirements.how_it_works.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "station.capability-consumer-producer-requirements.how_it_works.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "station.capability-consumer-producer-requirements.how_it_works.3": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "station.capability-architecture-platform-decisions.title": "Decisões de arquitetura e plataforma da capacidade", - "station.capability-architecture-platform-decisions.description": "Decisões de arquitetura e plataforma da capacidade clarifica a capacidade, consumidores, produtores, expectativas de serviço, riscos, evidências e próximas decisões ao nível reutilizável.", - "station.capability-architecture-platform-decisions.why_it_matters": "O Capability Cycle permanece acima do estilo de implementação e só referencia detalhes de API, integração, workflow, produto de dados ou aplicação após a decisão de estilo.", - "station.capability-architecture-platform-decisions.apply_in_work": "", - "station.capability-architecture-platform-decisions.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "station.capability-architecture-platform-decisions.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "station.capability-architecture-platform-decisions.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "station.capability-architecture-platform-decisions.outcomes.3": "Resultados preparados para a estação seguinte", - "station.capability-architecture-platform-decisions.how_it_works": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "station.capability-architecture-platform-decisions.how_it_works.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "station.capability-architecture-platform-decisions.how_it_works.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "station.capability-architecture-platform-decisions.how_it_works.3": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "station.capability-solution-interaction-design.title": "Desenho da solução e interação da capacidade", - "station.capability-solution-interaction-design.description": "Desenho da solução e interação da capacidade clarifica a capacidade, consumidores, produtores, expectativas de serviço, riscos, evidências e próximas decisões ao nível reutilizável.", - "station.capability-solution-interaction-design.why_it_matters": "O Capability Cycle permanece acima do estilo de implementação e só referencia detalhes de API, integração, workflow, produto de dados ou aplicação após a decisão de estilo.", - "station.capability-solution-interaction-design.apply_in_work": "", - "station.capability-solution-interaction-design.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "station.capability-solution-interaction-design.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "station.capability-solution-interaction-design.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "station.capability-solution-interaction-design.outcomes.3": "Resultados preparados para a estação seguinte", - "station.capability-solution-interaction-design.how_it_works": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "station.capability-solution-interaction-design.how_it_works.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "station.capability-solution-interaction-design.how_it_works.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "station.capability-solution-interaction-design.how_it_works.3": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "station.capability-delivery-operations.title": "Entrega e operações da capacidade", - "station.capability-delivery-operations.description": "Entrega e operações da capacidade clarifica a capacidade, consumidores, produtores, expectativas de serviço, riscos, evidências e próximas decisões ao nível reutilizável.", - "station.capability-delivery-operations.why_it_matters": "O Capability Cycle permanece acima do estilo de implementação e só referencia detalhes de API, integração, workflow, produto de dados ou aplicação após a decisão de estilo.", - "station.capability-delivery-operations.apply_in_work": "", - "station.capability-delivery-operations.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "station.capability-delivery-operations.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "station.capability-delivery-operations.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "station.capability-delivery-operations.outcomes.3": "Resultados preparados para a estação seguinte", - "station.capability-delivery-operations.how_it_works": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "station.capability-delivery-operations.how_it_works.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "station.capability-delivery-operations.how_it_works.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "station.capability-delivery-operations.how_it_works.3": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "station.capability-readiness-assurance.title": "Garantia de prontidão da capacidade", - "station.capability-readiness-assurance.description": "Garantia de prontidão da capacidade clarifica a capacidade, consumidores, produtores, expectativas de serviço, riscos, evidências e próximas decisões ao nível reutilizável.", - "station.capability-readiness-assurance.why_it_matters": "O Capability Cycle permanece acima do estilo de implementação e só referencia detalhes de API, integração, workflow, produto de dados ou aplicação após a decisão de estilo.", - "station.capability-readiness-assurance.apply_in_work": "", - "station.capability-readiness-assurance.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "station.capability-readiness-assurance.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "station.capability-readiness-assurance.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "station.capability-readiness-assurance.outcomes.3": "Resultados preparados para a estação seguinte", - "station.capability-readiness-assurance.how_it_works": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "station.capability-readiness-assurance.how_it_works.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "station.capability-readiness-assurance.how_it_works.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "station.capability-readiness-assurance.how_it_works.3": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "station.capability-publishing-enablement.title": "Publicação e enablement da capacidade", - "station.capability-publishing-enablement.description": "Publicação e enablement da capacidade clarifica a capacidade, consumidores, produtores, expectativas de serviço, riscos, evidências e próximas decisões ao nível reutilizável.", - "station.capability-publishing-enablement.why_it_matters": "O Capability Cycle permanece acima do estilo de implementação e só referencia detalhes de API, integração, workflow, produto de dados ou aplicação após a decisão de estilo.", - "station.capability-publishing-enablement.apply_in_work": "", - "station.capability-publishing-enablement.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "station.capability-publishing-enablement.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "station.capability-publishing-enablement.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "station.capability-publishing-enablement.outcomes.3": "Resultados preparados para a estação seguinte", - "station.capability-publishing-enablement.how_it_works": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "station.capability-publishing-enablement.how_it_works.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "station.capability-publishing-enablement.how_it_works.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "station.capability-publishing-enablement.how_it_works.3": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação.", - "station.capability-monitoring-improvement.title": "Monitorização e melhoria da capacidade", - "station.capability-monitoring-improvement.description": "Monitorização e melhoria da capacidade clarifica a capacidade, consumidores, produtores, expectativas de serviço, riscos, evidências e próximas decisões ao nível reutilizável.", - "station.capability-monitoring-improvement.why_it_matters": "O Capability Cycle permanece acima do estilo de implementação e só referencia detalhes de API, integração, workflow, produto de dados ou aplicação após a decisão de estilo.", - "station.capability-monitoring-improvement.apply_in_work": "", - "station.capability-monitoring-improvement.outcomes": "Decisão de capacidade ou artefacto de trabalho documentado", - "station.capability-monitoring-improvement.outcomes.1": "Consumidores, produtores, owners, evidências, restrições e expectativas de serviço clarificados", - "station.capability-monitoring-improvement.outcomes.2": "Riscos, pressupostos, próximos passos e impactos de ciclo de vida visíveis", - "station.capability-monitoring-improvement.outcomes.3": "Resultados preparados para a estação seguinte", - "station.capability-monitoring-improvement.how_it_works": "Clarifique o propósito da capacidade, consumidores, produtores, escopo e evidências.", - "station.capability-monitoring-improvement.how_it_works.1": "Documente decisões, responsabilidades, expectativas de serviço, riscos e artefactos necessários.", - "station.capability-monitoring-improvement.how_it_works.2": "Use o resultado para arquitetura, desenho, entrega, prontidão, publicação ou melhoria.", - "station.capability-monitoring-improvement.how_it_works.3": "Use guias de API, integração, workflow, produto de dados ou aplicação apenas após selecionar o estilo de implementação." + "station.monitoring-and-improving.how_it_works.3": "Aprendizagem e decisão de ciclo de vida: que suposições da hipótese foram suportadas ou rejeitadas, e a solução deve ser melhorada, expandida, restringida, redesenhada, pausada ou retirada?" } diff --git a/src/data/method/station-criteria.json b/src/data/method/station-criteria.json index 1007760..1e9501b 100644 --- a/src/data/method/station-criteria.json +++ b/src/data/method/station-criteria.json @@ -1,155 +1,163 @@ { - "api-product-strategy": [ - "metrics-feedback-available", - "business-goals-defined", - "market-research-done", - "stakeholder-approval" - ], - "api-consumer-experience": [ - "api-opportunity-documented", - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "api-platform-architecture": [ - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "api-design": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "api-delivery": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "api-audit": [ - "architecture-patterns-validated", - "design-reflects-business-value", - "api-description-available", - "api-consistency", - "api-contract-tested" - ], - "api-publishing": [ - "audit-passed", - "audit-reports-shared", - "api-ready-for-publishing", - "api-documentation-ready" - ], - "monitoring-and-improving": [ - "api-documentation-ready", - "consumer-support-ready", - "legal-compliance-clear" - ], - "integration-capability-strategy": [ - "metrics-feedback-available", - "business-goals-defined", - "market-research-done", - "stakeholder-approval" - ], - "integration-consumer-requirements-onboarding": [ - "api-opportunity-documented", - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "integration-architecture-platform-decisions": [ - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "integration-solution-design": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "integration-delivery-operations": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "integration-readiness-assurance": [ - "architecture-patterns-validated", - "design-reflects-business-value", - "api-description-available", - "api-consistency", - "api-contract-tested" - ], - "integration-publishing-enablement": [ - "audit-passed", - "audit-reports-shared", - "api-ready-for-publishing", - "api-documentation-ready" - ], - "integration-monitoring-improvement": [ - "api-documentation-ready", - "consumer-support-ready", - "legal-compliance-clear" - ], - "capability-strategy": [ - "metrics-feedback-available", - "business-goals-defined", - "market-research-done", - "stakeholder-approval" - ], - "capability-consumer-producer-requirements": [ - "api-opportunity-documented", - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "capability-architecture-platform-decisions": [ - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "capability-solution-interaction-design": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "capability-delivery-operations": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "capability-readiness-assurance": [ - "architecture-patterns-validated", - "design-reflects-business-value", - "api-description-available", - "api-consistency", - "api-contract-tested" - ], - "capability-publishing-enablement": [ - "audit-passed", - "audit-reports-shared", - "api-ready-for-publishing", - "api-documentation-ready" - ], - "capability-monitoring-improvement": [ - "api-documentation-ready", - "consumer-support-ready", - "legal-compliance-clear" - ] + "default": { + "api-product-strategy": [ + "metrics-feedback-available", + "business-goals-defined", + "market-research-done", + "stakeholder-approval" + ], + "api-consumer-experience": [ + "api-opportunity-documented", + "api-reusability", + "hide-backend-discrepancies", + "value-prop-validated", + "consumer-segments-identified", + "api-roadmap-defined" + ], + "api-platform-architecture": [ + "api-reusability", + "hide-backend-discrepancies", + "value-prop-validated", + "consumer-segments-identified", + "api-roadmap-defined" + ], + "api-design": [ + "architecture-patterns-validated", + "hide-backend-discrepancies", + "design-reflects-business-value", + "api-consistency" + ], + "api-delivery": [ + "architecture-patterns-validated", + "hide-backend-discrepancies", + "design-reflects-business-value", + "api-consistency" + ], + "api-audit": [ + "architecture-patterns-validated", + "design-reflects-business-value", + "api-description-available", + "api-consistency", + "api-contract-tested" + ], + "api-publishing": [ + "audit-passed", + "audit-reports-shared", + "api-ready-for-publishing", + "api-documentation-ready" + ], + "monitoring-and-improving": [ + "api-documentation-ready", + "consumer-support-ready", + "legal-compliance-clear" + ] + }, + "byCycle": { + "capability-productization-cycle": { + "api-product-strategy": [ + "metrics-feedback-available", + "business-goals-defined", + "market-research-done", + "stakeholder-approval" + ], + "api-consumer-experience": [ + "api-opportunity-documented", + "api-reusability", + "hide-backend-discrepancies", + "value-prop-validated", + "consumer-segments-identified", + "api-roadmap-defined" + ], + "api-platform-architecture": [ + "api-reusability", + "hide-backend-discrepancies", + "value-prop-validated", + "consumer-segments-identified", + "api-roadmap-defined" + ], + "api-design": [ + "architecture-patterns-validated", + "hide-backend-discrepancies", + "design-reflects-business-value", + "api-consistency" + ], + "api-delivery": [ + "architecture-patterns-validated", + "hide-backend-discrepancies", + "design-reflects-business-value", + "api-consistency" + ], + "api-audit": [ + "architecture-patterns-validated", + "design-reflects-business-value", + "api-description-available", + "api-consistency", + "api-contract-tested" + ], + "api-publishing": [ + "audit-passed", + "audit-reports-shared", + "api-ready-for-publishing", + "api-documentation-ready" + ], + "monitoring-and-improving": [ + "api-documentation-ready", + "consumer-support-ready", + "legal-compliance-clear" + ] + }, + "integration-productization-cycle": { + "api-product-strategy": [ + "metrics-feedback-available", + "business-goals-defined", + "market-research-done", + "stakeholder-approval" + ], + "api-consumer-experience": [ + "api-opportunity-documented", + "api-reusability", + "hide-backend-discrepancies", + "value-prop-validated", + "consumer-segments-identified", + "api-roadmap-defined" + ], + "api-platform-architecture": [ + "api-reusability", + "hide-backend-discrepancies", + "value-prop-validated", + "consumer-segments-identified", + "api-roadmap-defined" + ], + "api-design": [ + "architecture-patterns-validated", + "hide-backend-discrepancies", + "design-reflects-business-value", + "api-consistency" + ], + "api-delivery": [ + "architecture-patterns-validated", + "hide-backend-discrepancies", + "design-reflects-business-value", + "api-consistency" + ], + "api-audit": [ + "architecture-patterns-validated", + "design-reflects-business-value", + "api-description-available", + "api-consistency", + "api-contract-tested" + ], + "api-publishing": [ + "audit-passed", + "audit-reports-shared", + "api-ready-for-publishing", + "api-documentation-ready" + ], + "monitoring-and-improving": [ + "api-documentation-ready", + "consumer-support-ready", + "legal-compliance-clear" + ] + } + } } diff --git a/src/data/method/stations.json b/src/data/method/stations.json index b760c93..e066be6 100644 --- a/src/data/method/stations.json +++ b/src/data/method/stations.json @@ -370,744 +370,6 @@ "incident-report", "roadmap" ] - }, - { - "id": "integration-capability-strategy", - "title": "station.integration-capability-strategy.title", - "slug": "method/integration-capability-strategy", - "order": 1, - "icon": "strategy-outline", - "description": "station.integration-capability-strategy.description", - "why_it_matters": "station.integration-capability-strategy.why_it_matters", - "outcomes": [ - "station.integration-capability-strategy.outcomes", - "station.integration-capability-strategy.outcomes.1", - "station.integration-capability-strategy.outcomes.2", - "station.integration-capability-strategy.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.integration-capability-strategy.how_it_works" - }, - { - "step": "station.integration-capability-strategy.how_it_works.1" - }, - { - "step": "station.integration-capability-strategy.how_it_works.2" - }, - { - "step": "station.integration-capability-strategy.how_it_works.3" - } - ], - "apply_in_work": "station.integration-capability-strategy.apply_in_work", - "lifecycleStage": "strategy", - "stationCriteria": [ - "metrics-feedback-available", - "business-goals-defined", - "market-research-done", - "stakeholder-approval" - ], - "expectedEvidenceTags": [ - "design-artifact", - "documentation", - "research", - "roadmap" - ] - }, - { - "id": "integration-consumer-requirements-onboarding", - "title": "station.integration-consumer-requirements-onboarding.title", - "slug": "method/integration-consumer-requirements-onboarding", - "order": 2, - "icon": "deployed-code-account-outline", - "description": "station.integration-consumer-requirements-onboarding.description", - "why_it_matters": "station.integration-consumer-requirements-onboarding.why_it_matters", - "outcomes": [ - "station.integration-consumer-requirements-onboarding.outcomes", - "station.integration-consumer-requirements-onboarding.outcomes.1", - "station.integration-consumer-requirements-onboarding.outcomes.2", - "station.integration-consumer-requirements-onboarding.outcomes.3" - ], - "how-it-works": [ - { - "step": "station.api-consumer-experience.how_it_works" - }, - { - "step": "station.api-consumer-experience.how_it_works.1" - }, - { - "step": "station.api-consumer-experience.how_it_works.2" - } - ], - "apply_in_work": "station.integration-consumer-requirements-onboarding.apply_in_work", - "lifecycleStage": "strategy", - "stationCriteria": [ - "api-opportunity-documented", - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "expectedEvidenceTags": [ - "design-artifact", - "documentation", - "consumer-feedback" - ], - "how_it_works": [ - { - "step": "station.integration-consumer-requirements-onboarding.how_it_works" - }, - { - "step": "station.integration-consumer-requirements-onboarding.how_it_works.1" - }, - { - "step": "station.integration-consumer-requirements-onboarding.how_it_works.2" - }, - { - "step": "station.integration-consumer-requirements-onboarding.how_it_works.3" - } - ] - }, - { - "id": "integration-architecture-platform-decisions", - "title": "station.integration-architecture-platform-decisions.title", - "slug": "method/integration-architecture-platform-decisions", - "order": 3, - "icon": "code-blocks-outline", - "description": "station.integration-architecture-platform-decisions.description", - "why_it_matters": "station.integration-architecture-platform-decisions.why_it_matters", - "outcomes": [ - "station.integration-architecture-platform-decisions.outcomes", - "station.integration-architecture-platform-decisions.outcomes.1", - "station.integration-architecture-platform-decisions.outcomes.2", - "station.integration-architecture-platform-decisions.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.integration-architecture-platform-decisions.how_it_works" - }, - { - "step": "station.integration-architecture-platform-decisions.how_it_works.1" - }, - { - "step": "station.integration-architecture-platform-decisions.how_it_works.2" - }, - { - "step": "station.integration-architecture-platform-decisions.how_it_works.3" - } - ], - "apply_in_work": "station.integration-architecture-platform-decisions.apply_in_work", - "lifecycleStage": "architecture", - "stationCriteria": [ - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "expectedEvidenceTags": [ - "architecture-decision", - "documentation", - "platform-config", - "metrics" - ] - }, - { - "id": "integration-solution-design", - "title": "station.integration-solution-design.title", - "slug": "method/integration-solution-design", - "order": 4, - "icon": "api", - "description": "station.integration-solution-design.description", - "why_it_matters": "station.integration-solution-design.why_it_matters", - "outcomes": [ - "station.integration-solution-design.outcomes", - "station.integration-solution-design.outcomes.1", - "station.integration-solution-design.outcomes.2", - "station.integration-solution-design.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.integration-solution-design.how_it_works" - }, - { - "step": "station.integration-solution-design.how_it_works.1" - }, - { - "step": "station.integration-solution-design.how_it_works.2" - }, - { - "step": "station.integration-solution-design.how_it_works.3" - } - ], - "apply_in_work": "station.integration-solution-design.apply_in_work", - "lifecycleStage": "design", - "stationCriteria": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "expectedEvidenceTags": [ - "spec", - "contract", - "design-artifact", - "documentation" - ] - }, - { - "id": "integration-delivery-operations", - "title": "station.integration-delivery-operations.title", - "slug": "method/integration-delivery-operations", - "order": 5, - "icon": "code", - "description": "station.integration-delivery-operations.description", - "why_it_matters": "station.integration-delivery-operations.why_it_matters", - "outcomes": [ - "station.integration-delivery-operations.outcomes", - "station.integration-delivery-operations.outcomes.1", - "station.integration-delivery-operations.outcomes.2", - "station.integration-delivery-operations.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.integration-delivery-operations.how_it_works" - }, - { - "step": "station.integration-delivery-operations.how_it_works.1" - }, - { - "step": "station.integration-delivery-operations.how_it_works.2" - }, - { - "step": "station.integration-delivery-operations.how_it_works.3" - }, - { - "step": "station.integration-delivery-operations.how_it_works.4" - }, - { - "step": "station.integration-delivery-operations.how_it_works.5" - } - ], - "apply_in_work": "station.integration-delivery-operations.apply_in_work", - "lifecycleStage": "delivery", - "stationCriteria": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "expectedEvidenceTags": [ - "implementation", - "pipeline-config", - "test-report", - "security-report" - ] - }, - { - "id": "integration-readiness-assurance", - "title": "station.integration-readiness-assurance.title", - "slug": "method/integration-readiness-assurance", - "order": 6, - "icon": "check-box-outline", - "description": "station.integration-readiness-assurance.description", - "why_it_matters": "station.integration-readiness-assurance.why_it_matters", - "outcomes": [ - "station.integration-readiness-assurance.outcomes", - "station.integration-readiness-assurance.outcomes.1", - "station.integration-readiness-assurance.outcomes.2", - "station.integration-readiness-assurance.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.integration-readiness-assurance.how_it_works" - }, - { - "step": "station.integration-readiness-assurance.how_it_works.1" - }, - { - "step": "station.integration-readiness-assurance.how_it_works.2" - }, - { - "step": "station.integration-readiness-assurance.how_it_works.3" - }, - { - "step": "station.integration-readiness-assurance.how_it_works.4" - }, - { - "step": "station.integration-readiness-assurance.how_it_works.5" - } - ], - "apply_in_work": "station.integration-readiness-assurance.apply_in_work", - "lifecycleStage": "publishing", - "stationCriteria": [ - "architecture-patterns-validated", - "design-reflects-business-value", - "api-description-available", - "api-consistency", - "api-contract-tested" - ], - "expectedEvidenceTags": [ - "audit-report", - "compliance-report", - "security-report", - "test-report" - ] - }, - { - "id": "integration-publishing-enablement", - "title": "station.integration-publishing-enablement.title", - "slug": "method/integration-publishing-enablement", - "order": 7, - "icon": "deployed-code-outline", - "description": "station.integration-publishing-enablement.description", - "why_it_matters": "station.integration-publishing-enablement.why_it_matters", - "outcomes": [ - "station.integration-publishing-enablement.outcomes", - "station.integration-publishing-enablement.outcomes.1", - "station.integration-publishing-enablement.outcomes.2", - "station.integration-publishing-enablement.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.integration-publishing-enablement.how_it_works" - }, - { - "step": "station.integration-publishing-enablement.how_it_works.1" - }, - { - "step": "station.integration-publishing-enablement.how_it_works.2" - }, - { - "step": "station.integration-publishing-enablement.how_it_works.3" - } - ], - "apply_in_work": "station.integration-publishing-enablement.apply_in_work", - "lifecycleStage": "publishing", - "stationCriteria": [ - "audit-passed", - "audit-reports-shared", - "api-ready-for-publishing", - "api-documentation-ready" - ], - "expectedEvidenceTags": [ - "gateway-config", - "developer-portal", - "documentation", - "release-record" - ] - }, - { - "id": "integration-monitoring-improvement", - "title": "station.integration-monitoring-improvement.title", - "slug": "method/integration-monitoring-improvement", - "order": 8, - "icon": "analytics-outline", - "description": "station.integration-monitoring-improvement.description", - "why_it_matters": "station.integration-monitoring-improvement.why_it_matters", - "outcomes": [ - "station.integration-monitoring-improvement.outcomes", - "station.integration-monitoring-improvement.outcomes.1", - "station.integration-monitoring-improvement.outcomes.2", - "station.integration-monitoring-improvement.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.integration-monitoring-improvement.how_it_works" - }, - { - "step": "station.integration-monitoring-improvement.how_it_works.1" - }, - { - "step": "station.integration-monitoring-improvement.how_it_works.2" - }, - { - "step": "station.integration-monitoring-improvement.how_it_works.3" - } - ], - "apply_in_work": "station.integration-monitoring-improvement.apply_in_work", - "lifecycleStage": "improving", - "stationCriteria": [ - "api-documentation-ready", - "consumer-support-ready", - "legal-compliance-clear" - ], - "expectedEvidenceTags": [ - "metrics", - "consumer-feedback", - "incident-report", - "roadmap" - ] - }, - { - "id": "capability-strategy", - "title": "station.capability-strategy.title", - "slug": "method/capability-strategy", - "order": 1, - "icon": "strategy-outline", - "description": "station.capability-strategy.description", - "why_it_matters": "station.capability-strategy.why_it_matters", - "outcomes": [ - "station.capability-strategy.outcomes", - "station.capability-strategy.outcomes.1", - "station.capability-strategy.outcomes.2", - "station.capability-strategy.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.capability-strategy.how_it_works" - }, - { - "step": "station.capability-strategy.how_it_works.1" - }, - { - "step": "station.capability-strategy.how_it_works.2" - }, - { - "step": "station.capability-strategy.how_it_works.3" - } - ], - "apply_in_work": "station.capability-strategy.apply_in_work", - "lifecycleStage": "strategy", - "stationCriteria": [ - "metrics-feedback-available", - "business-goals-defined", - "market-research-done", - "stakeholder-approval" - ], - "expectedEvidenceTags": [ - "design-artifact", - "documentation", - "research", - "roadmap" - ] - }, - { - "id": "capability-consumer-producer-requirements", - "title": "station.capability-consumer-producer-requirements.title", - "slug": "method/capability-consumer-producer-requirements", - "order": 2, - "icon": "deployed-code-account-outline", - "description": "station.capability-consumer-producer-requirements.description", - "why_it_matters": "station.capability-consumer-producer-requirements.why_it_matters", - "outcomes": [ - "station.capability-consumer-producer-requirements.outcomes", - "station.capability-consumer-producer-requirements.outcomes.1", - "station.capability-consumer-producer-requirements.outcomes.2", - "station.capability-consumer-producer-requirements.outcomes.3" - ], - "how-it-works": [ - { - "step": "station.api-consumer-experience.how_it_works" - }, - { - "step": "station.api-consumer-experience.how_it_works.1" - }, - { - "step": "station.api-consumer-experience.how_it_works.2" - } - ], - "apply_in_work": "station.capability-consumer-producer-requirements.apply_in_work", - "lifecycleStage": "strategy", - "stationCriteria": [ - "api-opportunity-documented", - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "expectedEvidenceTags": [ - "design-artifact", - "documentation", - "consumer-feedback" - ], - "how_it_works": [ - { - "step": "station.capability-consumer-producer-requirements.how_it_works" - }, - { - "step": "station.capability-consumer-producer-requirements.how_it_works.1" - }, - { - "step": "station.capability-consumer-producer-requirements.how_it_works.2" - }, - { - "step": "station.capability-consumer-producer-requirements.how_it_works.3" - } - ] - }, - { - "id": "capability-architecture-platform-decisions", - "title": "station.capability-architecture-platform-decisions.title", - "slug": "method/capability-architecture-platform-decisions", - "order": 3, - "icon": "code-blocks-outline", - "description": "station.capability-architecture-platform-decisions.description", - "why_it_matters": "station.capability-architecture-platform-decisions.why_it_matters", - "outcomes": [ - "station.capability-architecture-platform-decisions.outcomes", - "station.capability-architecture-platform-decisions.outcomes.1", - "station.capability-architecture-platform-decisions.outcomes.2", - "station.capability-architecture-platform-decisions.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.capability-architecture-platform-decisions.how_it_works" - }, - { - "step": "station.capability-architecture-platform-decisions.how_it_works.1" - }, - { - "step": "station.capability-architecture-platform-decisions.how_it_works.2" - }, - { - "step": "station.capability-architecture-platform-decisions.how_it_works.3" - } - ], - "apply_in_work": "station.capability-architecture-platform-decisions.apply_in_work", - "lifecycleStage": "architecture", - "stationCriteria": [ - "api-reusability", - "hide-backend-discrepancies", - "value-prop-validated", - "consumer-segments-identified", - "api-roadmap-defined" - ], - "expectedEvidenceTags": [ - "architecture-decision", - "documentation", - "platform-config", - "metrics" - ] - }, - { - "id": "capability-solution-interaction-design", - "title": "station.capability-solution-interaction-design.title", - "slug": "method/capability-solution-interaction-design", - "order": 4, - "icon": "api", - "description": "station.capability-solution-interaction-design.description", - "why_it_matters": "station.capability-solution-interaction-design.why_it_matters", - "outcomes": [ - "station.capability-solution-interaction-design.outcomes", - "station.capability-solution-interaction-design.outcomes.1", - "station.capability-solution-interaction-design.outcomes.2", - "station.capability-solution-interaction-design.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.capability-solution-interaction-design.how_it_works" - }, - { - "step": "station.capability-solution-interaction-design.how_it_works.1" - }, - { - "step": "station.capability-solution-interaction-design.how_it_works.2" - }, - { - "step": "station.capability-solution-interaction-design.how_it_works.3" - } - ], - "apply_in_work": "station.capability-solution-interaction-design.apply_in_work", - "lifecycleStage": "design", - "stationCriteria": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "expectedEvidenceTags": [ - "spec", - "contract", - "design-artifact", - "documentation" - ] - }, - { - "id": "capability-delivery-operations", - "title": "station.capability-delivery-operations.title", - "slug": "method/capability-delivery-operations", - "order": 5, - "icon": "code", - "description": "station.capability-delivery-operations.description", - "why_it_matters": "station.capability-delivery-operations.why_it_matters", - "outcomes": [ - "station.capability-delivery-operations.outcomes", - "station.capability-delivery-operations.outcomes.1", - "station.capability-delivery-operations.outcomes.2", - "station.capability-delivery-operations.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.capability-delivery-operations.how_it_works" - }, - { - "step": "station.capability-delivery-operations.how_it_works.1" - }, - { - "step": "station.capability-delivery-operations.how_it_works.2" - }, - { - "step": "station.capability-delivery-operations.how_it_works.3" - }, - { - "step": "station.capability-delivery-operations.how_it_works.4" - }, - { - "step": "station.capability-delivery-operations.how_it_works.5" - } - ], - "apply_in_work": "station.capability-delivery-operations.apply_in_work", - "lifecycleStage": "delivery", - "stationCriteria": [ - "architecture-patterns-validated", - "hide-backend-discrepancies", - "design-reflects-business-value", - "api-consistency" - ], - "expectedEvidenceTags": [ - "implementation", - "pipeline-config", - "test-report", - "security-report" - ] - }, - { - "id": "capability-readiness-assurance", - "title": "station.capability-readiness-assurance.title", - "slug": "method/capability-readiness-assurance", - "order": 6, - "icon": "check-box-outline", - "description": "station.capability-readiness-assurance.description", - "why_it_matters": "station.capability-readiness-assurance.why_it_matters", - "outcomes": [ - "station.capability-readiness-assurance.outcomes", - "station.capability-readiness-assurance.outcomes.1", - "station.capability-readiness-assurance.outcomes.2", - "station.capability-readiness-assurance.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.capability-readiness-assurance.how_it_works" - }, - { - "step": "station.capability-readiness-assurance.how_it_works.1" - }, - { - "step": "station.capability-readiness-assurance.how_it_works.2" - }, - { - "step": "station.capability-readiness-assurance.how_it_works.3" - }, - { - "step": "station.capability-readiness-assurance.how_it_works.4" - }, - { - "step": "station.capability-readiness-assurance.how_it_works.5" - } - ], - "apply_in_work": "station.capability-readiness-assurance.apply_in_work", - "lifecycleStage": "publishing", - "stationCriteria": [ - "architecture-patterns-validated", - "design-reflects-business-value", - "api-description-available", - "api-consistency", - "api-contract-tested" - ], - "expectedEvidenceTags": [ - "audit-report", - "compliance-report", - "security-report", - "test-report" - ] - }, - { - "id": "capability-publishing-enablement", - "title": "station.capability-publishing-enablement.title", - "slug": "method/capability-publishing-enablement", - "order": 7, - "icon": "deployed-code-outline", - "description": "station.capability-publishing-enablement.description", - "why_it_matters": "station.capability-publishing-enablement.why_it_matters", - "outcomes": [ - "station.capability-publishing-enablement.outcomes", - "station.capability-publishing-enablement.outcomes.1", - "station.capability-publishing-enablement.outcomes.2", - "station.capability-publishing-enablement.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.capability-publishing-enablement.how_it_works" - }, - { - "step": "station.capability-publishing-enablement.how_it_works.1" - }, - { - "step": "station.capability-publishing-enablement.how_it_works.2" - }, - { - "step": "station.capability-publishing-enablement.how_it_works.3" - } - ], - "apply_in_work": "station.capability-publishing-enablement.apply_in_work", - "lifecycleStage": "publishing", - "stationCriteria": [ - "audit-passed", - "audit-reports-shared", - "api-ready-for-publishing", - "api-documentation-ready" - ], - "expectedEvidenceTags": [ - "gateway-config", - "developer-portal", - "documentation", - "release-record" - ] - }, - { - "id": "capability-monitoring-improvement", - "title": "station.capability-monitoring-improvement.title", - "slug": "method/capability-monitoring-improvement", - "order": 8, - "icon": "analytics-outline", - "description": "station.capability-monitoring-improvement.description", - "why_it_matters": "station.capability-monitoring-improvement.why_it_matters", - "outcomes": [ - "station.capability-monitoring-improvement.outcomes", - "station.capability-monitoring-improvement.outcomes.1", - "station.capability-monitoring-improvement.outcomes.2", - "station.capability-monitoring-improvement.outcomes.3" - ], - "how_it_works": [ - { - "step": "station.capability-monitoring-improvement.how_it_works" - }, - { - "step": "station.capability-monitoring-improvement.how_it_works.1" - }, - { - "step": "station.capability-monitoring-improvement.how_it_works.2" - }, - { - "step": "station.capability-monitoring-improvement.how_it_works.3" - } - ], - "apply_in_work": "station.capability-monitoring-improvement.apply_in_work", - "lifecycleStage": "improving", - "stationCriteria": [ - "api-documentation-ready", - "consumer-support-ready", - "legal-compliance-clear" - ], - "expectedEvidenceTags": [ - "metrics", - "consumer-feedback", - "incident-report", - "roadmap" - ] } ] }, diff --git a/src/lib/method-engine.js b/src/lib/method-engine.js index 2a51c08..c39e4a9 100644 --- a/src/lib/method-engine.js +++ b/src/lib/method-engine.js @@ -308,6 +308,16 @@ export function getStationCriteriaMap() { return readJson(resolveMethodFile("station-criteria.json")); } +export function resolveStationCriteria(stationCriteriaMap, stationId, cycleId = DEFAULT_CYCLE_ID) { + if (Array.isArray(stationCriteriaMap?.[stationId])) { + return stationCriteriaMap[stationId]; + } + + return stationCriteriaMap?.byCycle?.[cycleId]?.[stationId] + || stationCriteriaMap?.default?.[stationId] + || []; +} + export function getCriteria() { return readJson(resolveMethodFile("criteria.json")); } @@ -447,7 +457,7 @@ export function buildStartData(locale = DEFAULT_LOCALE, cycleId = DEFAULT_CYCLE_ : translate(station.description, stationLabels), suggestedForNewApi: index === 0, stakeholders: buildStationStakeholderData(station.id, locale, cycle.id), - criteria: (stationCriteriaMap[station.id] || []).map((criterionId) => ({ + criteria: resolveStationCriteria(stationCriteriaMap, station.id, cycle.id).map((criterionId) => ({ id: criterionId, label: translate(`criterion.${criterionId}`, criteriaLabels) })) diff --git a/src/schemas/station-criteria.schema.json b/src/schemas/station-criteria.schema.json index b259da9..f900a0f 100644 --- a/src/schemas/station-criteria.schema.json +++ b/src/schemas/station-criteria.schema.json @@ -1,11 +1,26 @@ { "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", - "patternProperties": { - ".*": { - "type": "array", - "items": {"type": "string"} + "required": ["default"], + "properties": { + "default": { + "$ref": "#/definitions/stationCriteriaMap" + }, + "byCycle": { + "type": "object", + "additionalProperties": { + "$ref": "#/definitions/stationCriteriaMap" + } } }, - "additionalProperties": false + "additionalProperties": false, + "definitions": { + "stationCriteriaMap": { + "type": "object", + "additionalProperties": { + "type": "array", + "items": {"type": "string"} + } + } + } } From 78df890a0472349ac8b92ddaf237648fb4951214 Mon Sep 17 00:00:00 2001 From: Marjukka Niinioja Date: Wed, 5 Aug 2026 18:05:06 +0300 Subject: [PATCH 3/3] 4.2.0 --- package-lock.json | 4 ++-- package.json | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/package-lock.json b/package-lock.json index 0b56394..db81b88 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "apiops-cycles-method-data", - "version": "4.1.1", + "version": "4.2.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "apiops-cycles-method-data", - "version": "4.1.1", + "version": "4.2.0", "license": "Apache-2.0", "workspaces": [ "packages/*" diff --git a/package.json b/package.json index d2ac94c..3160517 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "apiops-cycles-method-data", - "version": "4.1.1", + "version": "4.2.0", "description": "APIOps Cycles Method data and canvases", "license": "Apache-2.0", "type": "module",