@forwardimpact/map 0.11.0
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/LICENSE +201 -0
- package/README.md +67 -0
- package/bin/fit-map.js +287 -0
- package/examples/behaviours/_index.yaml +8 -0
- package/examples/behaviours/outcome_ownership.yaml +43 -0
- package/examples/behaviours/polymathic_knowledge.yaml +41 -0
- package/examples/behaviours/precise_communication.yaml +39 -0
- package/examples/behaviours/relentless_curiosity.yaml +37 -0
- package/examples/behaviours/systems_thinking.yaml +40 -0
- package/examples/capabilities/_index.yaml +8 -0
- package/examples/capabilities/business.yaml +205 -0
- package/examples/capabilities/delivery.yaml +1001 -0
- package/examples/capabilities/people.yaml +68 -0
- package/examples/capabilities/reliability.yaml +349 -0
- package/examples/capabilities/scale.yaml +1672 -0
- package/examples/copilot-setup-steps.yaml +25 -0
- package/examples/devcontainer.yaml +21 -0
- package/examples/disciplines/_index.yaml +6 -0
- package/examples/disciplines/data_engineering.yaml +68 -0
- package/examples/disciplines/engineering_management.yaml +61 -0
- package/examples/disciplines/software_engineering.yaml +68 -0
- package/examples/drivers.yaml +202 -0
- package/examples/framework.yaml +73 -0
- package/examples/levels.yaml +115 -0
- package/examples/questions/behaviours/outcome_ownership.yaml +228 -0
- package/examples/questions/behaviours/polymathic_knowledge.yaml +275 -0
- package/examples/questions/behaviours/precise_communication.yaml +248 -0
- package/examples/questions/behaviours/relentless_curiosity.yaml +248 -0
- package/examples/questions/behaviours/systems_thinking.yaml +238 -0
- package/examples/questions/capabilities/business.yaml +107 -0
- package/examples/questions/capabilities/delivery.yaml +101 -0
- package/examples/questions/capabilities/people.yaml +106 -0
- package/examples/questions/capabilities/reliability.yaml +105 -0
- package/examples/questions/capabilities/scale.yaml +104 -0
- package/examples/questions/skills/architecture_design.yaml +115 -0
- package/examples/questions/skills/cloud_platforms.yaml +105 -0
- package/examples/questions/skills/code_quality.yaml +162 -0
- package/examples/questions/skills/data_modeling.yaml +107 -0
- package/examples/questions/skills/devops.yaml +111 -0
- package/examples/questions/skills/full_stack_development.yaml +118 -0
- package/examples/questions/skills/sre_practices.yaml +113 -0
- package/examples/questions/skills/stakeholder_management.yaml +116 -0
- package/examples/questions/skills/team_collaboration.yaml +106 -0
- package/examples/questions/skills/technical_writing.yaml +110 -0
- package/examples/self-assessments.yaml +64 -0
- package/examples/stages.yaml +191 -0
- package/examples/tracks/_index.yaml +5 -0
- package/examples/tracks/platform.yaml +47 -0
- package/examples/tracks/sre.yaml +46 -0
- package/examples/vscode-settings.yaml +21 -0
- package/package.json +49 -0
- package/schema/json/behaviour-questions.schema.json +95 -0
- package/schema/json/behaviour.schema.json +73 -0
- package/schema/json/capability-questions.schema.json +95 -0
- package/schema/json/capability.schema.json +229 -0
- package/schema/json/defs.schema.json +132 -0
- package/schema/json/discipline.schema.json +123 -0
- package/schema/json/drivers.schema.json +48 -0
- package/schema/json/framework.schema.json +68 -0
- package/schema/json/levels.schema.json +121 -0
- package/schema/json/self-assessments.schema.json +52 -0
- package/schema/json/skill-questions.schema.json +83 -0
- package/schema/json/stages.schema.json +88 -0
- package/schema/json/track.schema.json +95 -0
- package/schema/rdf/behaviour-questions.ttl +128 -0
- package/schema/rdf/behaviour.ttl +130 -0
- package/schema/rdf/capability.ttl +466 -0
- package/schema/rdf/defs.ttl +396 -0
- package/schema/rdf/discipline.ttl +313 -0
- package/schema/rdf/drivers.ttl +84 -0
- package/schema/rdf/framework.ttl +166 -0
- package/schema/rdf/levels.ttl +357 -0
- package/schema/rdf/self-assessments.ttl +147 -0
- package/schema/rdf/skill-questions.ttl +155 -0
- package/schema/rdf/stages.ttl +166 -0
- package/schema/rdf/track.ttl +225 -0
- package/src/index-generator.js +65 -0
- package/src/index.js +44 -0
- package/src/levels.js +553 -0
- package/src/loader.js +608 -0
- package/src/modifiers.js +23 -0
- package/src/schema-validation.js +438 -0
- package/src/validation.js +2136 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to the Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2026 Dick Olsson
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
# @forwardimpact/map
|
|
2
|
+
|
|
3
|
+
A public site describing the data model for consumption by AI agents and
|
|
4
|
+
engineers.
|
|
5
|
+
|
|
6
|
+
## Role in the Vision
|
|
7
|
+
|
|
8
|
+
The Map product is the fundamental underpinning of all Forward Impact products.
|
|
9
|
+
It defines how engineering competencies, career progression, and agent
|
|
10
|
+
capabilities are structured\u2014and publishes that structure in
|
|
11
|
+
machine-readable formats so AI agents can reliably interpret and work with
|
|
12
|
+
career framework data.
|
|
13
|
+
|
|
14
|
+
Making the data model well understood is a first-class goal. By publishing JSON
|
|
15
|
+
Schema and RDF/SHACL definitions alongside canonical example data, we ensure
|
|
16
|
+
that every consumer—human or AI—shares a consistent understanding of the data
|
|
17
|
+
model.
|
|
18
|
+
|
|
19
|
+
## What It Does
|
|
20
|
+
|
|
21
|
+
- **Public data model** — JSON Schema and RDF/SHACL definitions for skills,
|
|
22
|
+
behaviours, disciplines, tracks, and levels
|
|
23
|
+
- **Data loading** — Parse and validate YAML data files
|
|
24
|
+
- **Validation** — Enforce referential integrity, required fields, and schema
|
|
25
|
+
compliance
|
|
26
|
+
- **Index generation** — Generate browser-compatible file indexes
|
|
27
|
+
- **Example data** — Canonical examples for testing and reference
|
|
28
|
+
|
|
29
|
+
## Usage
|
|
30
|
+
|
|
31
|
+
```sh
|
|
32
|
+
# Validate all data files
|
|
33
|
+
npx fit-map validate
|
|
34
|
+
|
|
35
|
+
# Generate index files for browser
|
|
36
|
+
npx fit-map generate-index
|
|
37
|
+
|
|
38
|
+
# Validate SHACL ontology
|
|
39
|
+
npx fit-map validate --shacl
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
## Package Exports
|
|
43
|
+
|
|
44
|
+
```javascript
|
|
45
|
+
import { loadAllData, loadCapabilities } from "@forwardimpact/map";
|
|
46
|
+
import { validateAll } from "@forwardimpact/map/validation";
|
|
47
|
+
import {
|
|
48
|
+
SKILL_PROFICIENCIES,
|
|
49
|
+
BEHAVIOUR_MATURITIES,
|
|
50
|
+
} from "@forwardimpact/map/levels";
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
## Data Structure
|
|
54
|
+
|
|
55
|
+
```
|
|
56
|
+
examples/
|
|
57
|
+
├── levels.yaml # Career levels
|
|
58
|
+
├── stages.yaml # Lifecycle stages
|
|
59
|
+
├── drivers.yaml # Organizational outcomes
|
|
60
|
+
├── disciplines/ # Engineering specialties
|
|
61
|
+
├── tracks/ # Work contexts (platform, SRE, etc.)
|
|
62
|
+
├── behaviours/ # Approach to work
|
|
63
|
+
├── capabilities/ # Skills grouped by area
|
|
64
|
+
└── questions/ # Interview questions
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
See the [documentation](../../docs/map/index.md) for details.
|
package/bin/fit-map.js
ADDED
|
@@ -0,0 +1,287 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
|
|
3
|
+
/**
|
|
4
|
+
* fit-map CLI
|
|
5
|
+
*
|
|
6
|
+
* Map validation and index generation for Engineering Pathway data.
|
|
7
|
+
*
|
|
8
|
+
* Commands:
|
|
9
|
+
* validate [--json|--shacl] Run validation (default: --json)
|
|
10
|
+
* generate-index [--data=PATH] Generate _index.yaml files
|
|
11
|
+
* --help Show help
|
|
12
|
+
*/
|
|
13
|
+
|
|
14
|
+
import { stat } from "fs/promises";
|
|
15
|
+
import { join, resolve, dirname } from "path";
|
|
16
|
+
import { fileURLToPath } from "url";
|
|
17
|
+
|
|
18
|
+
const __filename = fileURLToPath(import.meta.url);
|
|
19
|
+
const __dirname = dirname(__filename);
|
|
20
|
+
|
|
21
|
+
/**
|
|
22
|
+
* Parse CLI arguments
|
|
23
|
+
*/
|
|
24
|
+
function parseArgs(args) {
|
|
25
|
+
const command = args[0];
|
|
26
|
+
const options = {};
|
|
27
|
+
|
|
28
|
+
for (let i = 1; i < args.length; i++) {
|
|
29
|
+
const arg = args[i];
|
|
30
|
+
if (arg.startsWith("--data=")) {
|
|
31
|
+
options.dataDir = arg.slice(7);
|
|
32
|
+
} else if (arg === "--help" || arg === "-h") {
|
|
33
|
+
options.help = true;
|
|
34
|
+
} else if (arg.startsWith("--")) {
|
|
35
|
+
const [key, value] = arg.slice(2).split("=");
|
|
36
|
+
options[key] = value ?? true;
|
|
37
|
+
}
|
|
38
|
+
}
|
|
39
|
+
|
|
40
|
+
return { command, options };
|
|
41
|
+
}
|
|
42
|
+
|
|
43
|
+
/**
|
|
44
|
+
* Check if a directory exists
|
|
45
|
+
*/
|
|
46
|
+
async function dirExists(path) {
|
|
47
|
+
try {
|
|
48
|
+
const stats = await stat(path);
|
|
49
|
+
return stats.isDirectory();
|
|
50
|
+
} catch {
|
|
51
|
+
return false;
|
|
52
|
+
}
|
|
53
|
+
}
|
|
54
|
+
|
|
55
|
+
/**
|
|
56
|
+
* Find the data directory
|
|
57
|
+
*/
|
|
58
|
+
async function findDataDir(providedPath) {
|
|
59
|
+
if (providedPath) {
|
|
60
|
+
const resolved = resolve(providedPath);
|
|
61
|
+
if (await dirExists(resolved)) {
|
|
62
|
+
return resolved;
|
|
63
|
+
}
|
|
64
|
+
throw new Error(`Data directory not found: ${providedPath}`);
|
|
65
|
+
}
|
|
66
|
+
|
|
67
|
+
// Check common locations
|
|
68
|
+
const candidates = [
|
|
69
|
+
join(process.cwd(), "data"),
|
|
70
|
+
join(process.cwd(), "examples"),
|
|
71
|
+
join(__dirname, "../examples"),
|
|
72
|
+
];
|
|
73
|
+
|
|
74
|
+
for (const candidate of candidates) {
|
|
75
|
+
if (await dirExists(candidate)) {
|
|
76
|
+
return candidate;
|
|
77
|
+
}
|
|
78
|
+
}
|
|
79
|
+
|
|
80
|
+
throw new Error(
|
|
81
|
+
"No data directory found. Use --data=PATH to specify location.",
|
|
82
|
+
);
|
|
83
|
+
}
|
|
84
|
+
|
|
85
|
+
/**
|
|
86
|
+
* Format validation results for display
|
|
87
|
+
*/
|
|
88
|
+
function formatValidationResults(result) {
|
|
89
|
+
const lines = [];
|
|
90
|
+
|
|
91
|
+
if (result.valid) {
|
|
92
|
+
lines.push("✅ Validation passed\n");
|
|
93
|
+
} else {
|
|
94
|
+
lines.push("❌ Validation failed\n");
|
|
95
|
+
lines.push("\nErrors:");
|
|
96
|
+
for (const error of result.errors) {
|
|
97
|
+
const path = error.path ? ` (${error.path})` : "";
|
|
98
|
+
lines.push(` • ${error.type}: ${error.message}${path}`);
|
|
99
|
+
}
|
|
100
|
+
}
|
|
101
|
+
|
|
102
|
+
if (result.warnings?.length > 0) {
|
|
103
|
+
lines.push("\nWarnings:");
|
|
104
|
+
for (const warning of result.warnings) {
|
|
105
|
+
const path = warning.path ? ` (${warning.path})` : "";
|
|
106
|
+
lines.push(` ⚠ ${warning.type}: ${warning.message}${path}`);
|
|
107
|
+
}
|
|
108
|
+
}
|
|
109
|
+
|
|
110
|
+
return lines.join("\n");
|
|
111
|
+
}
|
|
112
|
+
|
|
113
|
+
/**
|
|
114
|
+
* Validate command
|
|
115
|
+
*/
|
|
116
|
+
async function runValidate(dataDir) {
|
|
117
|
+
console.log(`🔍 Validating data in: ${dataDir}\n`);
|
|
118
|
+
|
|
119
|
+
const { runSchemaValidation, loadAllData } = await import("../src/index.js");
|
|
120
|
+
|
|
121
|
+
// Load data first
|
|
122
|
+
const data = await loadAllData(dataDir, { validate: false });
|
|
123
|
+
|
|
124
|
+
// Run full validation
|
|
125
|
+
const result = await runSchemaValidation(dataDir, data);
|
|
126
|
+
|
|
127
|
+
console.log(formatValidationResults(result));
|
|
128
|
+
|
|
129
|
+
// Print summary
|
|
130
|
+
console.log("\n📊 Data Summary:");
|
|
131
|
+
console.log(` Skills: ${data.skills?.length || 0}`);
|
|
132
|
+
console.log(` Behaviours: ${data.behaviours?.length || 0}`);
|
|
133
|
+
console.log(` Disciplines: ${data.disciplines?.length || 0}`);
|
|
134
|
+
console.log(` Tracks: ${data.tracks?.length || 0}`);
|
|
135
|
+
console.log(` Levels: ${data.levels?.length || 0}`);
|
|
136
|
+
console.log(` Drivers: ${data.drivers?.length || 0}`);
|
|
137
|
+
|
|
138
|
+
return result.valid ? 0 : 1;
|
|
139
|
+
}
|
|
140
|
+
|
|
141
|
+
/**
|
|
142
|
+
* Generate index command
|
|
143
|
+
*/
|
|
144
|
+
async function runGenerateIndex(dataDir) {
|
|
145
|
+
console.log(`📁 Generating index files in: ${dataDir}\n`);
|
|
146
|
+
|
|
147
|
+
const { generateAllIndexes } = await import("../src/index.js");
|
|
148
|
+
|
|
149
|
+
const results = await generateAllIndexes(dataDir);
|
|
150
|
+
|
|
151
|
+
for (const [dir, files] of Object.entries(results)) {
|
|
152
|
+
if (files.error) {
|
|
153
|
+
console.log(`❌ ${dir}/_index.yaml: ${files.error}`);
|
|
154
|
+
} else {
|
|
155
|
+
console.log(`✅ ${dir}/_index.yaml (${files.length} files)`);
|
|
156
|
+
}
|
|
157
|
+
}
|
|
158
|
+
|
|
159
|
+
return 0;
|
|
160
|
+
}
|
|
161
|
+
|
|
162
|
+
/**
|
|
163
|
+
* SHACL validation command
|
|
164
|
+
*/
|
|
165
|
+
async function runValidateShacl() {
|
|
166
|
+
console.log("🔍 Validating SHACL schema syntax...\n");
|
|
167
|
+
|
|
168
|
+
const rdfDir = join(__dirname, "../schema/rdf");
|
|
169
|
+
|
|
170
|
+
try {
|
|
171
|
+
const { default: N3 } = await import("n3");
|
|
172
|
+
const { readFile, readdir } = await import("fs/promises");
|
|
173
|
+
|
|
174
|
+
// Find all .ttl files in the RDF directory
|
|
175
|
+
const files = await readdir(rdfDir);
|
|
176
|
+
const ttlFiles = files.filter((f) => f.endsWith(".ttl")).sort();
|
|
177
|
+
|
|
178
|
+
if (ttlFiles.length === 0) {
|
|
179
|
+
console.error("❌ No .ttl files found in schema/rdf/\n");
|
|
180
|
+
return 1;
|
|
181
|
+
}
|
|
182
|
+
|
|
183
|
+
let totalQuads = 0;
|
|
184
|
+
const errors = [];
|
|
185
|
+
|
|
186
|
+
for (const file of ttlFiles) {
|
|
187
|
+
const filePath = join(rdfDir, file);
|
|
188
|
+
const turtleContent = await readFile(filePath, "utf-8");
|
|
189
|
+
|
|
190
|
+
try {
|
|
191
|
+
const parser = new N3.Parser({ format: "text/turtle" });
|
|
192
|
+
const quads = parser.parse(turtleContent);
|
|
193
|
+
totalQuads += quads.length;
|
|
194
|
+
console.log(` ✓ ${file} (${quads.length} triples)`);
|
|
195
|
+
} catch (error) {
|
|
196
|
+
errors.push({ file, error: error.message });
|
|
197
|
+
console.log(` ✗ ${file}: ${error.message}`);
|
|
198
|
+
}
|
|
199
|
+
}
|
|
200
|
+
|
|
201
|
+
console.log();
|
|
202
|
+
if (errors.length > 0) {
|
|
203
|
+
console.error(`❌ SHACL syntax errors in ${errors.length} file(s)\n`);
|
|
204
|
+
return 1;
|
|
205
|
+
}
|
|
206
|
+
|
|
207
|
+
console.log(
|
|
208
|
+
`✅ SHACL syntax valid (${ttlFiles.length} files, ${totalQuads} triples)\n`,
|
|
209
|
+
);
|
|
210
|
+
return 0;
|
|
211
|
+
} catch (error) {
|
|
212
|
+
console.error(`❌ SHACL validation error: ${error.message}\n`);
|
|
213
|
+
return 1;
|
|
214
|
+
}
|
|
215
|
+
}
|
|
216
|
+
|
|
217
|
+
/**
|
|
218
|
+
* Show help
|
|
219
|
+
*/
|
|
220
|
+
function showHelp() {
|
|
221
|
+
console.log(`
|
|
222
|
+
fit-map - Data validation for Engineering Pathway
|
|
223
|
+
|
|
224
|
+
Usage:
|
|
225
|
+
fit-map <command> [options]
|
|
226
|
+
|
|
227
|
+
Commands:
|
|
228
|
+
validate Run validation (default: JSON schema validation)
|
|
229
|
+
generate-index Generate _index.yaml files for directories
|
|
230
|
+
|
|
231
|
+
Options:
|
|
232
|
+
--json JSON schema + referential validation (default)
|
|
233
|
+
--shacl SHACL schema syntax validation
|
|
234
|
+
--data=PATH Path to data directory (default: ./data or ./examples)
|
|
235
|
+
--help, -h Show this help message
|
|
236
|
+
|
|
237
|
+
Examples:
|
|
238
|
+
fit-map validate
|
|
239
|
+
fit-map validate --shacl
|
|
240
|
+
fit-map validate --data=./my-data
|
|
241
|
+
fit-map generate-index
|
|
242
|
+
`);
|
|
243
|
+
}
|
|
244
|
+
|
|
245
|
+
/**
|
|
246
|
+
* Main entry point
|
|
247
|
+
*/
|
|
248
|
+
async function main() {
|
|
249
|
+
const { command, options } = parseArgs(process.argv.slice(2));
|
|
250
|
+
|
|
251
|
+
if (options.help || !command) {
|
|
252
|
+
showHelp();
|
|
253
|
+
process.exit(command ? 0 : 1);
|
|
254
|
+
}
|
|
255
|
+
|
|
256
|
+
try {
|
|
257
|
+
let exitCode = 0;
|
|
258
|
+
|
|
259
|
+
switch (command) {
|
|
260
|
+
case "validate": {
|
|
261
|
+
if (options.shacl) {
|
|
262
|
+
exitCode = await runValidateShacl();
|
|
263
|
+
} else {
|
|
264
|
+
const dataDir = await findDataDir(options.dataDir);
|
|
265
|
+
exitCode = await runValidate(dataDir);
|
|
266
|
+
}
|
|
267
|
+
break;
|
|
268
|
+
}
|
|
269
|
+
case "generate-index": {
|
|
270
|
+
const dataDir = await findDataDir(options.dataDir);
|
|
271
|
+
exitCode = await runGenerateIndex(dataDir);
|
|
272
|
+
break;
|
|
273
|
+
}
|
|
274
|
+
default:
|
|
275
|
+
console.error(`Unknown command: ${command}`);
|
|
276
|
+
showHelp();
|
|
277
|
+
exitCode = 1;
|
|
278
|
+
}
|
|
279
|
+
|
|
280
|
+
process.exit(exitCode);
|
|
281
|
+
} catch (error) {
|
|
282
|
+
console.error(`Error: ${error.message}`);
|
|
283
|
+
process.exit(1);
|
|
284
|
+
}
|
|
285
|
+
}
|
|
286
|
+
|
|
287
|
+
main();
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/behaviour.schema.json
|
|
2
|
+
|
|
3
|
+
name: Own the Outcome
|
|
4
|
+
human:
|
|
5
|
+
description:
|
|
6
|
+
Business outcomes trump engineering elegance. Embrace extreme ownership of
|
|
7
|
+
what you build—not just code quality, but business relationships, impact
|
|
8
|
+
metrics, and end-to-end results. Accept technical debt when it enables
|
|
9
|
+
faster business value, but own the consequences. AI may generate the code,
|
|
10
|
+
but responsibility for outcomes remains with you.
|
|
11
|
+
maturityDescriptions:
|
|
12
|
+
emerging:
|
|
13
|
+
Takes responsibility for assigned tasks with supervision; follows through
|
|
14
|
+
when reminded; asks for help appropriately; understands that work serves
|
|
15
|
+
business goals
|
|
16
|
+
developing:
|
|
17
|
+
Owns task completion independently; reviews AI-generated code critically;
|
|
18
|
+
makes pragmatic trade-offs between speed and polish; takes responsibility
|
|
19
|
+
for understanding code before shipping; considers business impact of
|
|
20
|
+
technical decisions
|
|
21
|
+
practicing:
|
|
22
|
+
Takes end-to-end ownership of features and business outcomes; accepts
|
|
23
|
+
technical debt intentionally when it accelerates value; builds trust
|
|
24
|
+
through rapid delivery of working solutions; owns stakeholder
|
|
25
|
+
relationships; balances quality with delivery speed
|
|
26
|
+
role_modeling:
|
|
27
|
+
Drives accountability culture focused on outcomes not deliverables; owns
|
|
28
|
+
business relationships and impact metrics across their function; makes
|
|
29
|
+
trade-offs between custom solutions and generalizable work; there is no "I
|
|
30
|
+
must run this by X"; ensures verification rigor for AI-generated code
|
|
31
|
+
exemplifying:
|
|
32
|
+
Defines organizational accountability standards focused on business
|
|
33
|
+
impact; shapes industry practices around outcome ownership in the AI era;
|
|
34
|
+
sponsors transformational initiatives with full outcome accountability;
|
|
35
|
+
recognized externally for ownership culture leadership
|
|
36
|
+
|
|
37
|
+
agent:
|
|
38
|
+
title: Own the outcome end-to-end
|
|
39
|
+
workingStyle: |
|
|
40
|
+
At each step:
|
|
41
|
+
1. Define success criteria before starting
|
|
42
|
+
2. Verify the change achieves the criteria
|
|
43
|
+
3. Don't hand off until you've validated the work
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/behaviour.schema.json
|
|
2
|
+
|
|
3
|
+
name: Be Polymath Oriented
|
|
4
|
+
human:
|
|
5
|
+
description:
|
|
6
|
+
Depth of expertise combined with breadth across multiple domains. Go beyond
|
|
7
|
+
T-shaped, building knowledge that spans technology, business, science, and
|
|
8
|
+
the pharmaceutical domain. Like Jim Gray, who made better architectural
|
|
9
|
+
decisions by understanding business beyond his database expertise, see
|
|
10
|
+
connections others miss.
|
|
11
|
+
maturityDescriptions:
|
|
12
|
+
emerging:
|
|
13
|
+
Recognizes that problems benefit from cross-disciplinary insights; shows
|
|
14
|
+
interest in domains beyond immediate technical requirements
|
|
15
|
+
developing:
|
|
16
|
+
Applies knowledge from one domain to inform decisions in another; studies
|
|
17
|
+
adjacent fields like design, business, or science; begins learning domain
|
|
18
|
+
language of business partners
|
|
19
|
+
practicing:
|
|
20
|
+
Bridges gaps between engineering, design, business, and science; rapidly
|
|
21
|
+
immerses in new domains; speaks the language of Commercial, Manufacturing,
|
|
22
|
+
or R&D; makes better decisions by understanding broader context
|
|
23
|
+
role_modeling:
|
|
24
|
+
Champions cross-disciplinary learning; creates holistic solutions spanning
|
|
25
|
+
technical and business domains; embodies the Renaissance Engineer ideal;
|
|
26
|
+
translates specialized knowledge into accessible explanations; thinks like
|
|
27
|
+
a business insider
|
|
28
|
+
exemplifying:
|
|
29
|
+
Shapes organizational learning strategy across disciplines; recognized
|
|
30
|
+
industry thought leader bridging technology and business; advises
|
|
31
|
+
executive leadership on cross-functional strategy; publishes on polymathic
|
|
32
|
+
approaches to engineering; influences industry hiring and development
|
|
33
|
+
practices
|
|
34
|
+
|
|
35
|
+
agent:
|
|
36
|
+
title: Apply cross-domain insight
|
|
37
|
+
workingStyle: |
|
|
38
|
+
When solving problems:
|
|
39
|
+
1. Draw on knowledge from multiple domains
|
|
40
|
+
2. Consider perspectives beyond pure technical implementation
|
|
41
|
+
3. Look for patterns that can be generalized
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/behaviour.schema.json
|
|
2
|
+
|
|
3
|
+
name: Communicate with Precision
|
|
4
|
+
human:
|
|
5
|
+
description:
|
|
6
|
+
In the age of AI, clarity becomes a superpower. Communicate with
|
|
7
|
+
precision—reducing ambiguity in specifications, requirements, and designs.
|
|
8
|
+
Natural language is inherently vague; AI can only generate accurate
|
|
9
|
+
solutions when given clear, unambiguous intent.
|
|
10
|
+
maturityDescriptions:
|
|
11
|
+
emerging:
|
|
12
|
+
Communicates basic technical concepts when prompted; participates in team
|
|
13
|
+
discussions; writes simple documentation
|
|
14
|
+
developing:
|
|
15
|
+
Writes clear documentation and specifications; reduces ambiguity in
|
|
16
|
+
requirements; crafts effective prompts for AI tools; adapts communication
|
|
17
|
+
style for different audiences
|
|
18
|
+
practicing:
|
|
19
|
+
Separates requirements, designs, and tasks with precision; enables AI to
|
|
20
|
+
generate accurate code through clear specifications; translates between
|
|
21
|
+
technical and business language; facilitates productive discussions
|
|
22
|
+
role_modeling:
|
|
23
|
+
Creates spec-driven development practices; mentors others on precise
|
|
24
|
+
communication; spans C-level executives to frontline workers; drives
|
|
25
|
+
clarity as a core value across their function; represents the organization
|
|
26
|
+
externally
|
|
27
|
+
exemplifying:
|
|
28
|
+
Shapes industry standards for technical communication; recognized
|
|
29
|
+
authority on spec-driven AI development; influences organizational
|
|
30
|
+
communication culture; publishes on precision in the AI era; keynotes at
|
|
31
|
+
industry conferences
|
|
32
|
+
|
|
33
|
+
agent:
|
|
34
|
+
title: Communicate with clarity
|
|
35
|
+
workingStyle: |
|
|
36
|
+
When providing output:
|
|
37
|
+
1. Separate blocking issues from suggestions
|
|
38
|
+
2. Explain the "why" behind each recommendation
|
|
39
|
+
3. Provide concrete examples or alternatives
|