@forwardimpact/schema 0.10.0 → 0.10.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -7
- package/examples/capabilities/business.yaml +15 -15
- package/examples/capabilities/delivery.yaml +18 -17
- package/examples/capabilities/people.yaml +13 -13
- package/examples/capabilities/reliability.yaml +19 -18
- package/examples/capabilities/scale.yaml +17 -16
- package/package.json +2 -2
- package/src/modifiers.js +1 -1
package/README.md
CHANGED
|
@@ -1,19 +1,27 @@
|
|
|
1
1
|
# @forwardimpact/schema
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
A public site describing the data model for consumption by AI agents and
|
|
4
|
+
engineers.
|
|
4
5
|
|
|
5
6
|
## Role in the Vision
|
|
6
7
|
|
|
7
|
-
The schema
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
8
|
+
The schema app is the fundamental underpinning of all Forward Impact apps. It
|
|
9
|
+
defines how engineering competencies, career progression, and agent capabilities
|
|
10
|
+
are structured—and publishes that structure in machine-readable formats so AI
|
|
11
|
+
agents can reliably interpret and work with career framework data.
|
|
12
|
+
|
|
13
|
+
Making the schema well understood is a first-class goal. By publishing JSON
|
|
14
|
+
Schema and RDF/SHACL definitions alongside canonical example data, we ensure
|
|
15
|
+
that every consumer—human or AI—shares a consistent understanding of the data
|
|
16
|
+
model.
|
|
11
17
|
|
|
12
18
|
## What It Does
|
|
13
19
|
|
|
14
|
-
- **
|
|
15
|
-
disciplines, tracks, and grades
|
|
20
|
+
- **Public data model** — JSON Schema and RDF/SHACL definitions for skills,
|
|
21
|
+
behaviours, disciplines, tracks, and grades
|
|
16
22
|
- **Data loading** — Parse and validate YAML data files
|
|
23
|
+
- **Validation** — Enforce referential integrity, required fields, and schema
|
|
24
|
+
compliance
|
|
17
25
|
- **Index generation** — Generate browser-compatible file indexes
|
|
18
26
|
- **Example data** — Canonical examples for testing and reference
|
|
19
27
|
|
|
@@ -9,37 +9,37 @@ description: |
|
|
|
9
9
|
and translating between technical and business contexts.
|
|
10
10
|
professionalResponsibilities:
|
|
11
11
|
awareness:
|
|
12
|
-
|
|
12
|
+
You understand the business context for your assigned work and communicate
|
|
13
13
|
progress clearly when asked
|
|
14
14
|
foundational:
|
|
15
|
-
|
|
16
|
-
to clarify requirements
|
|
15
|
+
You connect your technical work to business outcomes, engage with
|
|
16
|
+
stakeholders to clarify requirements
|
|
17
17
|
working:
|
|
18
|
-
|
|
18
|
+
You translate business needs into technical solutions, manage stakeholder
|
|
19
19
|
expectations, and articulate technical decisions in business terms
|
|
20
20
|
practitioner:
|
|
21
|
-
|
|
21
|
+
You drive business outcomes through technical solutions across your area,
|
|
22
22
|
influence product roadmaps, and partner effectively with business
|
|
23
23
|
stakeholders
|
|
24
24
|
expert:
|
|
25
|
-
|
|
26
|
-
at executive level, and
|
|
27
|
-
business
|
|
25
|
+
You shape technology-driven business strategy, represent the technical
|
|
26
|
+
perspective at executive level, and are recognized as a bridge between
|
|
27
|
+
engineering and business
|
|
28
28
|
managementResponsibilities:
|
|
29
29
|
awareness:
|
|
30
|
-
|
|
31
|
-
with guidance
|
|
30
|
+
You understand business context and communicate team progress to
|
|
31
|
+
stakeholders with guidance
|
|
32
32
|
foundational:
|
|
33
|
-
|
|
33
|
+
You align team priorities with business objectives, manage stakeholder
|
|
34
34
|
relationships, and communicate team impact
|
|
35
35
|
working:
|
|
36
|
-
|
|
37
|
-
relationships, and ensure team delivers business value
|
|
36
|
+
You translate business strategy into team objectives, own stakeholder
|
|
37
|
+
relationships, and ensure your team delivers business value
|
|
38
38
|
practitioner:
|
|
39
|
-
|
|
39
|
+
You partner with business leaders to shape strategy for your area, influence
|
|
40
40
|
direction across teams, and deliver measurable business impact
|
|
41
41
|
expert:
|
|
42
|
-
|
|
42
|
+
You shape technology-driven business strategy, represent engineering at
|
|
43
43
|
executive level, and own strategic business outcomes
|
|
44
44
|
skills:
|
|
45
45
|
- id: stakeholder_management
|
|
@@ -10,36 +10,37 @@ description: |
|
|
|
10
10
|
and rapid prototyping.
|
|
11
11
|
professionalResponsibilities:
|
|
12
12
|
awareness:
|
|
13
|
-
|
|
13
|
+
You complete assigned implementation tasks within established patterns with
|
|
14
14
|
guidance from senior engineers
|
|
15
15
|
foundational:
|
|
16
|
-
|
|
17
|
-
your code fits the broader system
|
|
16
|
+
You deliver small features end-to-end with minimal guidance, understanding
|
|
17
|
+
how your code fits the broader system
|
|
18
18
|
working:
|
|
19
|
-
|
|
20
|
-
trade-offs to ship value on time
|
|
19
|
+
You own feature delivery from design through deployment, making sound
|
|
20
|
+
technical trade-offs to ship value on time
|
|
21
21
|
practitioner:
|
|
22
|
-
|
|
23
|
-
others through hands-on contributions, and ensure engineering
|
|
22
|
+
You lead technical delivery of complex projects across multiple teams,
|
|
23
|
+
unblock others through hands-on contributions, and ensure engineering
|
|
24
|
+
quality
|
|
24
25
|
expert:
|
|
25
|
-
|
|
26
|
-
engineering delivery practices across the business unit, and
|
|
26
|
+
You drive delivery of the most critical technical initiatives, establish
|
|
27
|
+
engineering delivery practices across the business unit, and are the
|
|
27
28
|
technical authority on high-stakes projects
|
|
28
29
|
managementResponsibilities:
|
|
29
30
|
awareness:
|
|
30
|
-
|
|
31
|
+
You track team progress and communicate status to stakeholders with guidance
|
|
31
32
|
foundational:
|
|
32
|
-
|
|
33
|
-
keeping stakeholders informed
|
|
33
|
+
You coordinate team delivery by managing dependencies, removing blockers,
|
|
34
|
+
and keeping stakeholders informed
|
|
34
35
|
working:
|
|
35
|
-
|
|
36
|
+
You own team delivery outcomes—balance scope, staffing, and timeline; make
|
|
36
37
|
resourcing decisions to meet commitments
|
|
37
38
|
practitioner:
|
|
38
|
-
|
|
39
|
-
and practices for your area, hold teams accountable, and escalate
|
|
40
|
-
risks
|
|
39
|
+
You drive delivery excellence across multiple teams, establish delivery
|
|
40
|
+
metrics and practices for your area, hold teams accountable, and escalate
|
|
41
|
+
cross-team risks
|
|
41
42
|
expert:
|
|
42
|
-
|
|
43
|
+
You shape delivery culture across the business unit, lead strategic delivery
|
|
43
44
|
transformations, and represent delivery commitments at executive level
|
|
44
45
|
skills:
|
|
45
46
|
- id: data_integration
|
|
@@ -9,35 +9,35 @@ description: |
|
|
|
9
9
|
and creating inclusive environments.
|
|
10
10
|
professionalResponsibilities:
|
|
11
11
|
awareness:
|
|
12
|
-
|
|
12
|
+
You contribute positively to team dynamics, are open to feedback, and learn
|
|
13
13
|
actively from colleagues
|
|
14
14
|
foundational:
|
|
15
|
-
|
|
15
|
+
You support teammates through pair programming, knowledge sharing, and
|
|
16
16
|
constructive code reviews
|
|
17
17
|
working:
|
|
18
|
-
|
|
19
|
-
interviews, and actively build team knowledge
|
|
18
|
+
You mentor junior engineers on technical topics, contribute to hiring
|
|
19
|
+
through interviews, and actively build team knowledge
|
|
20
20
|
practitioner:
|
|
21
|
-
|
|
22
|
-
across your area, and shape team technical culture
|
|
21
|
+
You coach multiple engineers on career growth, lead hiring for technical
|
|
22
|
+
roles across your area, and shape team technical culture
|
|
23
23
|
expert:
|
|
24
|
-
|
|
24
|
+
You develop technical leaders, shape engineering talent strategy across the
|
|
25
25
|
business unit, and build high-performing engineering teams
|
|
26
26
|
managementResponsibilities:
|
|
27
27
|
awareness:
|
|
28
|
-
|
|
28
|
+
You build positive relationships with team members and seek feedback on your
|
|
29
29
|
leadership
|
|
30
30
|
foundational:
|
|
31
|
-
|
|
31
|
+
You conduct effective 1:1s, provide regular feedback, support individual
|
|
32
32
|
development, and recognize contributions
|
|
33
33
|
working:
|
|
34
|
-
|
|
34
|
+
You manage team performance, own hiring decisions, create inclusive team
|
|
35
35
|
environments, and handle difficult conversations
|
|
36
36
|
practitioner:
|
|
37
|
-
|
|
38
|
-
area, make promotion decisions, and shape team culture
|
|
37
|
+
You develop and retain talent across teams, build leadership pipelines for
|
|
38
|
+
your area, make promotion decisions, and shape team culture
|
|
39
39
|
expert:
|
|
40
|
-
|
|
40
|
+
You develop senior leaders, shape talent strategy across the business unit,
|
|
41
41
|
build high-performing teams, and own succession planning
|
|
42
42
|
skills:
|
|
43
43
|
- id: team_collaboration
|
|
@@ -10,38 +10,39 @@ description: |
|
|
|
10
10
|
and infrastructure management.
|
|
11
11
|
professionalResponsibilities:
|
|
12
12
|
awareness:
|
|
13
|
-
|
|
14
|
-
and participate in on-call rotations with guidance
|
|
13
|
+
You follow security and operational guidelines, escalate issues
|
|
14
|
+
appropriately, and participate in on-call rotations with guidance
|
|
15
15
|
foundational:
|
|
16
|
-
|
|
17
|
-
contribute effectively to incident response
|
|
16
|
+
You implement reliability practices in your code, create basic monitoring,
|
|
17
|
+
and contribute effectively to incident response
|
|
18
18
|
working:
|
|
19
|
-
|
|
19
|
+
You design for reliability, implement comprehensive monitoring and alerting,
|
|
20
20
|
lead incident response, and drive post-incident improvements
|
|
21
21
|
practitioner:
|
|
22
|
-
|
|
23
|
-
initiatives for your area, mentor engineers on reliability
|
|
24
|
-
drive reliability culture
|
|
22
|
+
You establish SLOs/SLIs across teams, build resilient systems, lead
|
|
23
|
+
reliability initiatives for your area, mentor engineers on reliability
|
|
24
|
+
practices, and drive reliability culture
|
|
25
25
|
expert:
|
|
26
|
-
|
|
27
|
-
management, pioneer new reliability practices, and
|
|
28
|
-
system resilience
|
|
26
|
+
You shape reliability strategy across the business unit, lead critical
|
|
27
|
+
incident management, pioneer new reliability practices, and are the
|
|
28
|
+
authority on system resilience
|
|
29
29
|
managementResponsibilities:
|
|
30
30
|
awareness:
|
|
31
|
-
|
|
31
|
+
You understand reliability requirements and support incident escalation
|
|
32
32
|
processes
|
|
33
33
|
foundational:
|
|
34
|
-
|
|
35
|
-
facilitate incident retrospectives
|
|
34
|
+
You ensure your team follows reliability practices, manage on-call
|
|
35
|
+
schedules, and facilitate incident retrospectives
|
|
36
36
|
working:
|
|
37
|
-
|
|
37
|
+
You own team reliability outcomes, manage incident response rotations, staff
|
|
38
38
|
reliability initiatives, and champion operational excellence
|
|
39
39
|
practitioner:
|
|
40
|
-
|
|
40
|
+
You drive reliability culture across teams, establish SLOs and incident
|
|
41
41
|
management processes for your area, and own cross-team reliability outcomes
|
|
42
42
|
expert:
|
|
43
|
-
|
|
44
|
-
management at executive level, and own enterprise reliability
|
|
43
|
+
You shape reliability strategy across the business unit, lead critical
|
|
44
|
+
incident management at executive level, and own enterprise reliability
|
|
45
|
+
outcomes
|
|
45
46
|
skills:
|
|
46
47
|
- id: service_management
|
|
47
48
|
name: Service Management
|
|
@@ -10,38 +10,39 @@ description: |
|
|
|
10
10
|
and technical decision-making.
|
|
11
11
|
professionalResponsibilities:
|
|
12
12
|
awareness:
|
|
13
|
-
|
|
14
|
-
from senior engineers
|
|
13
|
+
You follow established architectural patterns and coding standards with
|
|
14
|
+
guidance from senior engineers
|
|
15
15
|
foundational:
|
|
16
|
-
|
|
17
|
-
and understand architectural trade-offs
|
|
16
|
+
You contribute to scalable designs, write quality code with appropriate
|
|
17
|
+
tests, and understand architectural trade-offs
|
|
18
18
|
working:
|
|
19
|
-
|
|
20
|
-
quality, and review others' designs
|
|
19
|
+
You design scalable components, make sound architectural decisions, ensure
|
|
20
|
+
code quality, and review others' designs
|
|
21
21
|
practitioner:
|
|
22
|
-
|
|
22
|
+
You lead architectural decisions for complex systems across teams, establish
|
|
23
23
|
quality standards for your area, mentor engineers on architecture, and own
|
|
24
24
|
technical debt strategy
|
|
25
25
|
expert:
|
|
26
|
-
|
|
27
|
-
architecture,
|
|
26
|
+
You define technical standards across the business unit, guide enterprise
|
|
27
|
+
architecture, are recognized externally for architectural expertise, and
|
|
28
28
|
drive innovation
|
|
29
29
|
managementResponsibilities:
|
|
30
30
|
awareness:
|
|
31
|
-
|
|
32
|
-
implications
|
|
31
|
+
You understand technical architecture decisions and their resource and
|
|
32
|
+
timeline implications
|
|
33
33
|
foundational:
|
|
34
|
-
|
|
34
|
+
You support team technical decisions, ensure alignment with architectural
|
|
35
35
|
standards, and escalate technical risks
|
|
36
36
|
working:
|
|
37
|
-
|
|
38
|
-
champion quality, and balance technical investment with
|
|
37
|
+
You facilitate architectural discussions, manage technical debt
|
|
38
|
+
prioritization, champion quality, and balance technical investment with
|
|
39
|
+
delivery
|
|
39
40
|
practitioner:
|
|
40
|
-
|
|
41
|
+
You drive technical excellence across teams, establish quality standards for
|
|
41
42
|
your area, own cross-team technical direction, and advise on architecture
|
|
42
43
|
trade-offs
|
|
43
44
|
expert:
|
|
44
|
-
|
|
45
|
+
You shape technical strategy across the business unit, guide enterprise
|
|
45
46
|
architecture governance, and represent technical priorities at executive
|
|
46
47
|
level
|
|
47
48
|
skills:
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@forwardimpact/schema",
|
|
3
|
-
"version": "0.10.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.10.2",
|
|
4
|
+
"description": "Public data model for career frameworks, consumed by AI agents and engineers",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|
|
7
7
|
"type": "git",
|
package/src/modifiers.js
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
* Skill Modifier Helpers for Validation
|
|
3
3
|
*
|
|
4
4
|
* Contains only the isCapability function needed for schema validation.
|
|
5
|
-
* Full modifier logic is in @forwardimpact/
|
|
5
|
+
* Full modifier logic is in @forwardimpact/libpathway.
|
|
6
6
|
*/
|
|
7
7
|
|
|
8
8
|
import { Capability } from "./levels.js";
|