OpenPing Technology
Core Values
Moving operations from "someone remembers" to "the framework guarantees it" — standards written as documents, judgements written as rules, rules written as scripts, scripts becoming gates.
Guaranteed by the Framework, Not by Memory
Standards written as documents, judgements written as rules, rules written as scripts, scripts becoming gates.
Seven Core Values
1. Documents Are the Authority
There is no such thing as "the way we pass it on by word of mouth". Every standard, every technology choice, every rejected option and the reason for rejecting it must be written down and dated. A fact is written once and only referenced elsewhere — write the same fact twice and the two will eventually diverge, and once they do, nobody knows which is correct.
2. The Index Comes Before the Content
Task guides are organised by type of work: one for network equipment installation, another for service deployment. Each task starts by updating the guide itself, then the standards it lists, and only then the target of the work. The order cannot be swapped — until the index is updated, you do not know what needs updating.
3. Production Separated From Acceptance
The party producing the work and the party accepting it must come from different model families. This is not a formality of double-checking; it exists because the same reasoning habit can both make an error and fail to see it. Without an acceptance report, the work is not complete.
4. Gate Placement Is Decided by Risk
When a document or a program is wrong, the error is still upstream of the repository and after-the-fact acceptance catches it; when an installation or deployment is wrong, the thing has already been done. Irreversible work therefore gets an additional gate beforehand — gate placement should be decided by when an error becomes irreversible, not by putting one on every line for the sake of symmetry.
5. Criteria Must Be Machine-Checkable
Every rule that leaves no room for judgement is written as a check script and run once before work begins and once before delivery. A rule written in a document is only an expectation; a rule written as a script is a mechanism — a recommendation with no checking mechanism is, in practice, the same as not having written it.
6. Classification and Boundaries
Data is classified by sensitivity and cross-referenced against the legal jurisdiction of each service provider; the highest class of customer-identifying data never leaves the network. Credentials and secrets have an explicit handling boundary: AI produces the structure that references a credential, people supply the credential itself. The test is whether, if this secret leaked, the holder could impersonate someone.
7. Keep the Reasons
What gets recorded is not only the conclusion but the explanation, the reasoning, the decision points and the considerations — including the options that were rejected and why. If the reason is not written down, the next person can only ask again; and a question asked a second time means the first answer was never kept.