Layer 01 · Knowledge

Turn scattered enterprise knowledge into governed, portable bundles.

Salesforce, Slack, Jira, Confluence, Zendesk, repositories, shared drives, databases, wikis, runbooks, and internal documentation each contain part of the operating truth. Hardpoint identifies the knowledge worth preserving, classifies ownership and sensitivity, models it as OKF concepts, carries provenance and lifecycle information forward, establishes review and refresh workflows, and makes approved bundles usable by enterprise agents and human operators.

Read the published specificationIndependent implementation practice

Open Knowledge Format is an open specification published by Google Cloud. Hardpoint is an independent implementation practice and is not a Google partner or Google-certified.

Why it matters

Most AI failures are knowledge failures wearing a model costume.

Swapping models rarely fixes a system that has no governed source of truth. These are the conditions we find most often.

Knowledge lives in prompts

The institutional understanding that makes an AI system useful is pasted into a chat window, owned by one person, and lost when the tool changes.

No version, no review

Nobody can answer what changed, when, or who approved it — so nobody can safely change anything.

Vendor-shaped

Knowledge encoded in one platform's format cannot move when pricing, capability or policy changes.

Unmeasurable

Without discrete artifacts there is nothing to evaluate, so quality is argued rather than tested.

Architecture

Source to bundle.

Each stage is a decision with an owner. Nothing moves forward because a crawler found it.

01Salesforce · Slack · Jira · Confluence · Zendesk · Git · Drives · Databases
02Source inventory and policy boundary
03Ownership · Authority · Sensitivity · Freshness · Exclusions
04Extract · Normalize · Deduplicate · Curate
05Concepts · Relationships · Provenance · Lifecycle
06OKF knowledge bundles
07Validation · Review · Git lifecycle
08Search · Retrieval · Agents · Applications
09Evaluation · Freshness · Deprecation

Candidate source environments

SalesforceSlackJiraConfluenceZendeskGit repositoriesShared drivesDatabasesWikisRunbooks

Product and company names are used only to illustrate potential source environments. No partnership or endorsement is implied. Hardpoint transforms selected knowledge domains and approved sources — not every record in every system.

Engagements

Three ways to buy this work.

Assessment first, then a bounded pilot, then a domain-by-domain program if the pilot earns it.

Knowledge

OKF Readiness Assessment

Fragmented knowledge that enterprise agents cannot reliably discover, trust, or maintain.

Client inputs

· List of candidate source systems
· Knowledge owners for each domain
· Sensitivity and retention policy

Hardpoint activities

· Source and ownership inventory
· Domain prioritization workshops
· Sensitivity and exclusion analysis
· Draft taxonomy and lifecycle modeling

Written deliverables

· Source and ownership inventory
· Knowledge-domain prioritization
· Sensitivity and exclusion rules
· Draft concept taxonomy
· Lifecycle and provenance requirements
· Bounded pilot recommendation

Engagement boundary

No bulk extraction and no custody of production content. Selected domains only.

Completion condition

A recommended pilot boundary is agreed with the knowledge owners.

Likely next phase

Enterprise OKF Transformation Pilot.

Start this engagement Read the practiceExplore a synthetic OKF transformation— publishing soon

Knowledge

Enterprise OKF Transformation Pilot

One business domain ready to be modeled, governed and consumed by agents or retrieval.

Client inputs

· One business domain
· Two or three approved source systems
· One or two agent or retrieval use cases
· A defined corpus boundary and evaluation question set

Hardpoint activities

· Extraction and normalization
· Concept and relationship modeling
· Provenance and lifecycle workflow design
· Git review process and consumer integration
· Evaluation harness construction

Written deliverables

· Extraction procedure
· Normalized staging model
· Illustrative or validated OKF bundle
· Provenance and lifecycle workflow
· Git review process
· Consumer integration
· Evaluation harness
· Operating handoff

Engagement boundary

Bounded to the agreed domain, sources and corpus. Not a universal enterprise conversion.

Completion condition

The pilot bundle passes the agreed evaluation set and ownership is transferred.

Likely next phase

Domain-by-domain knowledge transformation program.

Start this engagement Read the practiceInspect sample artifacts— publishing soon

Knowledge

Domain-by-domain Knowledge Transformation Program

For organizations that have completed a pilot and want to extend transformation across additional business domains at a controlled cadence.

Written deliverables

· Domain sequence and prioritization
· Per-domain corpus boundary and exclusions
· Reusable extraction and review procedure
· Bundle validation reports
· Evaluation results per domain
· Operating ownership per domain

Engagement boundary

One domain at a time, each with its own boundary and acceptance. The program can be stopped after any domain.

Sample output

What a transformation actually produces.

Representative deliverables

— Source inventory
— Ownership map
— Exclusion policy
— Concept taxonomy
— Sample frontmatter
— Relationships
— Provenance
— Freshness and lifecycle status
— Validation report
— Evaluation question set
— Operating workflow

Illustrative bundle frontmatter

concept: refund-authority
title: Refund authority thresholds
owner: finance-ops
authority: policy-committee
sensitivity: internal
freshness_sla: 14d
status: approved
provenance:
  - salesforce:policy-object/4821
  - confluence:finance/refunds
relationships:
  - depends_on: escalation-matrix
  - supersedes: refund-authority-2023

Illustrative structure only. Hardpoint does not describe a bundle as specification- conformant unless it has passed the relevant validation.

This page does not accept uploads. Do not submit confidential source material here; source access is established only after qualification and appropriate agreements.

Interactive reference environment

Explore a synthetic OKF transformation.

The Architecture Lab walks a synthetic knowledge domain from source systems to a governed bundle and then into a governed query. Synthetic data only.

Synthetic reference environment

Knowledge source

01Knowledge source· done

Salesforce
Confluence
Jira
Git
Runbooks

02Governed OKF concept· pending

concept: refund-authority
owner: finance-ops
sensitivity: internal
freshness: 14d
provenance: 3 sources

03Workload class· pending

High-Consequence

04Eligible routes· pending

Local 8B · owned hardwareeligible
Regional API · mid tiereligible
Frontier API · primaryeligible
Offshore API · lowest priceeligible

Exclusions are stated, not implied: Capability below acceptance; Locality policy excluded.

05Fallback· pending

Primary path degrades mid-request. The predetermined fallback takes the workload before the operator is paged.

06Routing Receipt· pending

class: high-consequence
eligible: 2 of 4
excluded: capability, locality
selected: frontier-api
fallback: regional-api (engaged)
retries: 1   latency: 2.4s
evaluation: passed
disposition: accepted

Explore a synthetic OKF transformation— publishing soon

Interactive reference environment · Synthetic data · No production systems connected

Inspect sample artifacts— publishing soon

Boundaries

What stays yours.

Hardpoint designs and implements the format, pipeline and governance. Content ownership stays with your subject-matter owners — a knowledge system nobody in the business owns will decay regardless of how well it is engineered. Advisory work is performed without taking custody of client data; where implementation requires access, it happens inside your environment under your controls.

Bring us the knowledge sprawl.

Wikis, PDFs, spreadsheets, Slack threads, three competing sources of truth and a chatbot that confidently cites the wrong one. That is the normal starting point.

Discuss an Architecture See engagement models Or book an architecture triage call