BARKLY LABS
STANDARD / LIVING DOCUMENT / 0.1
BARKLY STANDARDDOC. 003

BUILDHUMAN.

The Barkly Standard is a living collection of principles, practices, and engineering decisions used throughout Barkly Labs to build technology that humans can understand, modify, contribute to, and make their own.

CURRENT VERSION0.1FOUNDATION / LIVING STANDARD
01 / OVERVIEW

TECHNOLOGYSHOULD EXPLAIN.

Barkly Labs builds software, research, tools, and experimental systems around a simple idea: humans should be able to understand the technology they use, build, and contribute to.

The Barkly Standard turns that idea into practical engineering principles. It guides architecture, interfaces, documentation, AI-assisted development, research, accessibility, experimentation, and collaboration.

It is intentionally not a finished rulebook. The laboratory is expected to learn, and the standard is expected to learn with it.

“Show the shape first. Reveal the details when the human asks for them.”
02 / PRINCIPLES
01
HUMAN FIRST
Technology should remain understandable and controllable by the people using it.
Barkly systems are designed around human understanding, agency, accessibility, and meaningful control. Technical capability alone is not enough if the human cannot understand what the system is doing.
02
SHAPE FIRST
Show the structure before requiring the human to understand the implementation.
Complex systems should reveal their major components, relationships, and purpose before exposing deeper implementation details. Complexity should be navigable rather than hidden.
03
INSPECTABLE
Systems should provide a path toward understanding how they work.
Projects should make their architecture, components, behavior, dependencies, assumptions, and limitations discoverable whenever practical.
04
DOCUMENTED
Important knowledge should not exist only inside someone's head.
Documentation is treated as part of the system itself. Projects should preserve not only what they do, but why important decisions were made.
05
EXPERIMENTAL
A laboratory must have room for ideas that might fail.
Experiments are allowed to be incomplete, strange, or unsuccessful. What matters is clearly identifying experimental work and preserving useful knowledge from it.
06
OPEN
Knowledge should be shareable, inspectable, and extendable whenever practical.
Barkly favors open development, reusable knowledge, and systems that other people can inspect, modify, fork, and contribute to.
07
ACCESSIBLE
Accessibility includes cognitive clarity as well as technical accessibility.
Barkly considers cognitive load, discoverability, clarity, navigation, and different ways humans interact with technology.
08
EVOLVING
The standard itself is allowed to change as the laboratory learns.
The Barkly Standard is a living document. New discoveries, failures, experiments, and better practices can change the standard over time.
03 / CORE PRINCIPLE
BARKLY / PRINCIPLE 001
SHOW THESHAPE FIRST.
Complex systems should reveal their structure before demanding that humans understand their deepest implementation details. The goal is not to remove complexity. The goal is to make complexity navigable.
01SYSTEM
02STRUCTURE
03BEHAVIOR
04IMPLEMENTATION
05DETAIL
04 / DEVELOPMENT LOOP
01ORIENT

Understand what exists before diving into implementation.

02STRUCTURE

Identify the major systems, components, and relationships.

03BUILD

Implement the system while preserving understandable boundaries.

04DOCUMENT

Record behavior, reasoning, limitations, and important decisions.

05TEST

Verify that the system behaves as intended.

06LEARN

Use results, failures, and discoveries to improve the system.

07EVOLVE

Update the standard when the laboratory learns something new.

05 / PRACTICES

THE
WORKING
RULES.

The Standard becomes useful when it changes how systems are actually built. These practices translate the underlying philosophy into everyday engineering decisions.

They are guidelines rather than bureaucracy. If following a rule makes the work less understandable, less accessible, or less useful, the rule should be questioned.

  1. 01Show the shape before the details.
  2. 02Make complexity navigable instead of unnecessarily hiding it.
  3. 03Document the reasoning behind important decisions.
  4. 04Preserve human understanding and agency.
  5. 05Treat documentation as part of engineering.
  6. 06Allow experiments to fail without pretending they are production systems.
  7. 07Make limitations and boundaries visible.
  8. 08Use AI as a tool while keeping humans responsible for the resulting system.
  9. 09Prefer openness when security, privacy, safety, and licensing permit it.
  10. 10Question the standard when following it makes the work worse.
06 / LIVING STANDARD

ALWAYS
EVOLVING.

The Barkly Standard is intentionally versioned. New projects, experiments, failures, discoveries, and contributions can change how the laboratory understands good engineering.

A future version may disagree with this one. That is not a failure of the standard. It is evidence that the laboratory learned something.

0.1 / FOUNDATION
Initial principles established for human-centered engineering, documentation, experimentation, openness, accessibility, and progressive disclosure.

PRACTICE
THE STANDARD.

The Standard is not intended to sit on a shelf. Barkly projects should demonstrate it in practice.

Barkly Docs, research projects, software systems, interfaces, and future experiments should all provide evidence of the principles being applied.

THE TEST
Can another human understand what exists, why it exists, how it works, and where they can contribute?

BUILDYOUR OWN.

Barkly Labs does not exist to make everyone build the same things. The Standard exists to create a foundation where people can bring their own ideas, skills, identities, experiments, and ways of thinking into an environment designed for understanding, contribution, and exploration.

READ THE FULL STANDARD →