docs: [verified] connect Strategy through practical Delivery journey
Build and publish Eldorado documentation / build (pull_request) Successful in 42s
Build and publish Eldorado documentation / build (pull_request) Successful in 42s
This commit is contained in:
1 parent
c934ddb5e0
commit
f7a68d7e37
50 files changed
+1573
-95
No files matched your search
@@ -33,4 +33,6 @@ Read the shared [collection and safeguards](./collection-and-safeguards.mdx) bef
|
||||
|
||||
Return to [Skills Measurement](./index.mdx).
|
||||
|
||||
In [Stage 01](../stage-01-skills-adoption.mdx), authorization to test an experimental revision is not general approved status. This contract counts approved-revision use only; do not relabel experimental pilot use to raise its numerator. [Adoption](../skills-adoption.mdx) still evaluates that pilot through independent work outcomes and [Quality's fitness evidence](../skills-quality.mdx). Use this reach measure only where its approved-revision population applies.
|
||||
|
||||
</div>
|
||||
@@ -10,7 +10,7 @@ description: Shared interpretation rules, event contracts and privacy safeguards
|
||||
**Target operating model — recommended contracts, not installed collection.** Registry inclusion does not require use, collection or baselining. All owner and cadence entries are proposals to confirm for selected metrics, not assigned responsibilities or approved schedules.
|
||||
|
||||
{/* preserved:start */}
|
||||
Introduction depends on the [roadmap gates](../roadmap.mdx); these pages do not describe installed controls or measured company results.
|
||||
Use these safeguards throughout the [Stage 01 journey](../stage-01-skills-adoption.mdx); these pages do not describe installed controls or measured company results.
|
||||
|
||||
### Decide what counts before counting
|
||||
|
||||
@@ -39,4 +39,6 @@ The privacy starting proposal is 30 days for raw structured analytics events and
|
||||
|
||||
Return to the [Skills Measurement index](./index.mdx) for every metric definition.
|
||||
|
||||
For the illustrative Delivery comparison, agree sources, permissions and independent acceptance before collection. Carry the population and gap record from [Baseline](../baseline.mdx) into [Adoption](../skills-adoption.mdx). Keep [Quality's qualification trials](../skills-quality.mdx) separate from live workflow starts; revised reports must preserve that boundary.
|
||||
|
||||
</div>
|
||||
@@ -25,13 +25,20 @@ Each entry explains meaning and applicability, calculation, required inputs and
|
||||
|
||||
To select a relevant subset and establish actual starting evidence, use [Baseline](../baseline.mdx). Pilot application belongs to [Adoption](../skills-adoption.mdx); ongoing interpretation belongs to [Maintenance](../skills-maintenance.mdx).
|
||||
|
||||
In the **illustrative Delivery workflow** from [Stage 01](../stage-01-skills-adoption.mdx), incomplete regression evidence is the improvement hypothesis. The workflow owner and independent Quality Engineering reviewer select contracts that can test it, then carry the same definitions into the baseline and pilot comparison. They can leave unrelated metrics unselected. This reference capability supports the whole journey; opening this page is not an execution gate.
|
||||
|
||||
## Metric definitions
|
||||
|
||||
Each contract is a prospective definition, not a rollout obligation. No live source or observed baseline is established. N and D refer to the numerator and denominator shown for that metric.
|
||||
|
||||
<details>
|
||||
<summary>Implementation status—not live telemetry</summary>
|
||||
|
||||
There are **16 contracts: 9 prototype calculations and 7 unimplemented metrics**. The prototype has no network collectors. None of these counts establishes live telemetry.
|
||||
|
||||
The nine calculations cover task success, selection precision and recall, change fail rate, deployment rework, escaped quality, policy effects, cost and the primary human-experience item. The seven omissions are supported bundle coverage, approved-workflow adoption, change lead time, deployment frequency, failed deployment recovery time, substantive-review coverage and workflow-specific business acceptance.
|
||||
|
||||
Each contract is a prospective definition, not a rollout obligation. No live source or observed baseline is established. N and D refer to the numerator and denominator shown for that metric.
|
||||
</details>
|
||||
|
||||
### Workflow effectiveness
|
||||
|
||||
@@ -55,6 +62,8 @@ Human effort is recorded as review/rework inputs where the cost contract support
|
||||
|
||||
**Are the skills fit for use and kept fit?** Qualify named skills and versions, observe supported use during adoption, and review or retire them in maintenance. Without applicable skills, bundles or enrolled use, skill-specific measures may be **N/A, not zero**. Once a population exists, missing observations are unknown, not evidence of non-use or good health.
|
||||
|
||||
**Fitness comes from [Quality's evaluation evidence](../skills-quality.mdx), not health proxies.** Compare named candidate and approved revisions against declared cases, independent artifact acceptance and mandatory safety checks. Retain regression results, failed trials and coverage limits. The five registry contracts below complement that report: selection tests relevance; support, use and review measures describe operating health. None replaces evidence that a skill produces useful, safe artifacts. Maintenance sends real failures and revision changes back to Quality for requalification.
|
||||
|
||||
1. [Skill selection precision](./skill-selection-precision.mdx) — **Prototype calculation.** Did the evaluated selection choose an applicable skill? Requires labeled qualification cases.
|
||||
2. [Skill selection recall](./skill-selection-recall.mdx) — **Prototype calculation.** Were expected skills selected? Requires the same labeled qualification population.
|
||||
3. [Supported bundle coverage](./supported-bundle-coverage.mdx) — **Unimplemented metric.** Are expected active installations on supported, non-revoked bundles/adapters?
|
||||
|
||||
@@ -33,4 +33,6 @@ Read the shared [collection and safeguards](./collection-and-safeguards.mdx) bef
|
||||
|
||||
Return to [Skills Measurement](./index.mdx).
|
||||
|
||||
Use this labeled-case result in [Quality's candidate evaluation](../skills-quality.mdx). Selecting the right skill is only one input: independently test artifact fitness, safe execution and revision regression before the owning approver considers a bounded pilot. It is not the live Delivery workflow's accepted-task rate.
|
||||
|
||||
</div>
|
||||
@@ -33,4 +33,6 @@ Read the shared [collection and safeguards](./collection-and-safeguards.mdx) bef
|
||||
|
||||
Return to [Skills Measurement](./index.mdx).
|
||||
|
||||
Use this labeled-case result alongside precision in [Quality's candidate evaluation](../skills-quality.mdx). Finding expected skills does not establish useful artifacts or safe execution. Preserve missing-case coverage and revision-regression evidence before a bounded pilot; do not pool evaluation cases with live Delivery tasks.
|
||||
|
||||
</div>
|
||||
@@ -33,4 +33,6 @@ Read the shared [collection and safeguards](./collection-and-safeguards.mdx) bef
|
||||
|
||||
Return to [Skills Measurement](./index.mdx).
|
||||
|
||||
[Maintenance](../skills-maintenance.mdx) uses this coverage signal to find overdue or ownerless revisions. A current date is not proof of effectiveness: substantive review must consider [Quality's fitness and regression evidence](../skills-quality.mdx), supported-client changes and live-workflow outcomes. Gaps trigger review or requalification, not a favorable health assumption.
|
||||
|
||||
</div>
|
||||
@@ -19,4 +19,6 @@ The executable covers validated success, selection precision/recall, change fail
|
||||
|
||||
Return to the [Skills Measurement index](./index.mdx) for every metric definition.
|
||||
|
||||
Use this fixture to check calculation and missing-evidence behavior before applying selected contracts in [Baseline](../baseline.mdx) or [Adoption](../skills-adoption.mdx). It is not the illustrative Delivery workflow's baseline and does not qualify a skill: [Quality](../skills-quality.mdx) requires independent, versioned artifact and safety evidence on declared evaluation cases.
|
||||
|
||||
</div>
|
||||
@@ -35,7 +35,7 @@ This contract belongs to **Workflow effectiveness**. Use the same matured-start
|
||||
|
||||
For **Skills effectiveness & health**, a predeclared slice of live workflow tasks using a named skill/version may reuse this contract unchanged. Keep the parent cohort visible, report exact versions and selection limits, and count each task once across retries, skills and clients. Overlapping skill slices must not be summed. This is descriptive evidence, not proof that the skill caused success.
|
||||
|
||||
A sandbox or qualification evaluation of a named skill/version is a different population and remains excluded by this contract. Declare its cases, skill/version, client/model configuration, acceptance rubric and observed results separately; never combine those cases with live workflow starts or present their results as this prototype's workflow rate. This page does not introduce an implemented skill-evaluation metric or an alternative formula. No applicable skill means that skill-specific evaluation is N/A, not a zero workflow success rate.
|
||||
A sandbox or qualification evaluation of a named skill/version is a different population and remains excluded by this contract. [Quality](../skills-quality.mdx) defines artifact-success and revision-regression evidence: declare cases, skill/version, client/model configuration, acceptance rubric and observed results separately; never combine those cases with live workflow starts or present their results as this prototype's workflow rate. This page does not introduce an implemented skill-evaluation metric or an alternative formula. No applicable skill means that skill-specific evaluation is N/A, not a zero workflow success rate.
|
||||
|
||||
Read the shared [collection and safeguards](./collection-and-safeguards.mdx) before collecting data; see the [synthetic example and limits](./synthetic-example.mdx).
|
||||
|
||||
|
||||
Reference in new issue
Block a user