Raw source view
shape_payloads/instances/company_profiles/accurotech.json
{
"shape_payload_id": "SP-COMPANY-PROFILE-ACCUROTECH-001",
"conforms_to_shape_pattern_template": "SPT-COMPANY-PROFILE-001",
"payload_version": "0.1.0",
"created": "2026-06-17",
"status": "day_three_architecture_seed",
"payload_policy": "No secrets, credentials, tokens, private customer payloads, concrete private observations, deployment secrets, or fabricated implementation claims.",
"profile_identity": {
"slug": "accurotech",
"display_name": "AccuroTech",
"entity_type": "company",
"aliases": [
"AccuroTech"
],
"related_domains": []
},
"source_provenance": {
"source_files": [
"docs/projects/accurotech/shape_stub.md",
"docs/company/project_index.md",
"catalogue/generated_indexes/shape_catalogue_project_alignment.md",
"accurotech_portashape_global_shape_catalogue_seed_dayone_base_v0_0_1.json"
],
"source_shape_ids": [
"AT-001",
"AT-002",
"AT-003",
"AT-004",
"AT-005",
"AT-006",
"REL-001",
"REL-002",
"REL-003",
"REL-004",
"REL-005",
"REL-006"
],
"source_namespaces": [
"AT",
"REL",
"RELZ",
"WF",
"TIME"
],
"source_status": "repository_grounded_extraction_with_catalogue_alignment",
"last_extraction_run_id": "day_three_true_value_extraction_2026-06-17"
},
"canon_status": {
"level": "scaffold",
"review_required": true,
"public_copy_approved": false,
"internal_site_ready": "draft_ready_after_extraction_review"
},
"website_sections": [
{
"section_id": "overview",
"title": "Overview",
"body": "AccuroTech is the parent company and operating ecosystem for a broad family of software projects, platforms, communities, reporting systems, creative outlets, automation tools, and ministry-aligned stewardship structures. Repository sources state that the ecosystem is early, iterative, internal-first/public-later, and not yet broadly launched as public production infrastructure. Implementation status: implemented in this repository only as documentation pages, company profile payloads, catalogue alignment notes, and Day-Two/Day-Three planning surfaces. Scaffolded project folders and Shape stubs exist. Runnable source code, deployment configuration, production readiness, active users, and operational data are not claimed.",
"source_refs": [
"docs/projects/accurotech/shape_stub.md",
"docs/company/project_index.md"
],
"importance": "required",
"editable": true,
"source_status": "seed_derived_repository_grounded"
},
{
"section_id": "ecosystem_role",
"title": "Role in the AccuroTech Ecosystem",
"body": "AccuroTech is the system-of-systems container for authority, meaning, structure, automation, publishing/community surfaces, observation/reporting surfaces, and WASHAD/Last Christian Church ministry governance. It preserves the core triad that XtraType gives meaning, CRE8 gives authority, and PortaShape gives structure.",
"source_refs": [
"docs/projects/accurotech/shape_stub.md",
"docs/company/ecosystem_map.md"
],
"importance": "required",
"editable": true,
"source_status": "seed_derived_repository_grounded"
},
{
"section_id": "shape_alignment",
"title": "Shape Catalogue Alignment",
"body": "Catalogue alignment: namespaces AT, REL, RELZ, WF, TIME. Representative Shape IDs: AT-001, AT-002, AT-003, AT-004, AT-005, AT-006, REL-001, REL-002, REL-003, REL-004, REL-005, REL-006. These are documentation/catalogue alignments only, not implementation or production claims.",
"source_refs": [
"docs/company/project_index.md",
"catalogue/generated_indexes/shape_catalogue_project_alignment.md",
"accurotech_portashape_global_shape_catalogue_seed_dayone_base_v0_0_1.json"
],
"importance": "required",
"editable": true,
"source_status": "catalogue_aligned"
},
{
"section_id": "internal_build_direction",
"title": "Internal Build Direction",
"body": "Internal build direction: review and approve canonical copy; promote the most relevant catalogue records into project-specific canon candidates; identify the first safe schema or workflow artifact; add source-basis notes for each claim; decide which cross-project relationships should become formal Shape relationship records; add validation rules, synthetic examples, and review workflows before connecting implementation repositories or modules. Missing fields requiring human input: human-approved canonical description, launch status, formal owner/steward, complete public domain inventory, repository-to-service mapping, exact implementation inventory outside this documentation scaffold, formal schemas, API boundaries, data-retention rules, and review workflows.",
"source_refs": [
"docs/projects/accurotech/shape_stub.md",
"roadmap/day_two_plan.md"
],
"importance": "recommended",
"editable": true,
"source_status": "repository_grounded_missing_fields"
}
],
"editable_fields": {
"all_fields_editable_in_internal_site": true,
"edit_storage": "write back to this Shape Payload JSON file",
"protected_fields": [
"shape_payload_id",
"conforms_to_shape_pattern_template"
]
},
"relationship_refs": {
"parent_profile_payload_ids": [],
"child_profile_payload_ids": [],
"related_profile_payload_ids": [],
"github_instantiation_payload_id": "SP-GITHUB-INSTANTIATION-ACCUROTECH-001",
"website_page_payload_id": "SP-WEBSITE-PAGE-ACCUROTECH-001"
}
}