Behavior Evaluation Protocol

Behavioral Evaluation Protocol (BEP)

https://chatgpt.com/share/69ecfce1-971c-83e8-86e7-474774b17753

Purpose

The Behavioral Evaluation Protocol (BEP) is used by Open Source Ecology (OSE) to evaluate participants based on real-world performance.

It exists to:

• Identify individuals who produce tangible results under constraint
• Filter out high-enthusiasm / low-execution behavior
• Evaluate collaborative reliability in team-based build environments
• Align all participation with Global Village Construction Set (GVCS) execution goals

The BEP is not a personality test. It is a production-based evaluation system.

Core Principle

Behavior is only valid if it predicts production.

Evaluation reduces to:

• Can the individual convert intent into build output?
• Is the output real, constrained, and replicable?

Evaluation Stack

Layer 1: Signal Acquisition (Observation)

Observe behavior without interpretation.

Track:

• Time to first action
• Specificity of language
• Awareness of constraints (time, cost, materials)
• Response latency under pressure
• Consistency between words and actions
• Ratio of discussion to building

No conclusions are made at this stage.

Layer 2: Behavioral Structuring (Patterning)

Convert observations into testable hypotheses.

Track:

• Baseline vs deviation
• Alignment between verbal and nonverbal behavior
• Indicators of commitment
• Indicators of cognitive load or avoidance
• Patterns of engagement or withdrawal

Output of this layer is hypotheses, not conclusions.

Layer 3: Elicitation and Testing

All hypotheses must be tested through action.

Standard tests:

• Compression Test

 Ask for a plan in 3 steps. Measures clarity and reduction of abstraction.

• Constraint Injection

 Introduce limits (time, cost, materials). Measures realism.

• Build Trigger

 Require a minimal version within a fixed short time. Measures execution bias.

• Documentation Test

 Require publishing of process. Measures clarity and openness.

• Iteration Test

 Require improvement based on feedback. Measures adaptability.

Layer 4: Outcome Validation

Only outcomes are considered valid evidence.

Track:

• Delivered artifacts (physical or digital)
• Time to delivery
• Replicability of output
• Integration with team outputs
• Economic and practical relevance

Scoring Model

Each dimension is scored from 0 to 5.

Execution Throughput

0 = no output 5 = consistent delivery under constraint

Reality Alignment

0 = ignores constraints 5 = designs within real limits

Signal to Noise Ratio

0 = abstract, verbose, unclear 5 = concise, specific, testable

Learning Velocity

0 = no improvement 5 = rapid iteration with visible progress

Collaborative Reliability

0 = disrupts coordination 5 = improves group performance

Documentation Quality

0 = non-transferable knowledge 5 = fully replicable documentation

Behavioral Archetypes

Builder

High execution, moderate communication Core contributor type

Integrator

Connects systems and people High leverage when grounded in execution

Narrator

Strong ideas, weak execution Requires strict testing

Drifter

Inconsistent participation High coordination cost

Illusionist

High enthusiasm, low constraint awareness Avoids testing and real-world validation

Red Flag Patterns

• Avoids time-bound tasks
• Rejects constraints as unnecessary
• Cannot produce minimal output
• Uses abstract or unfalsifiable language
• Resists documentation
• Repeatedly pivots without completion

Green Flag Patterns

• Builds before extended discussion
• Uses numbers, materials, and constraints naturally
• Publishes work openly
• Iterates based on feedback
• Delivers within defined limits

Deployment Model

Phase 1: Entry Filter (1 to 3 days)

• Run Compression Test
• Run Build Trigger
• Run Documentation Test
• Require immediate real output

Phase 2: Short Sprint (1 to 2 weeks)

• Assign real project role
• Track all scoring dimensions
• Observe collaboration behavior

Phase 3: Integration Decision

Decide based on:

• Consistency of output
• Compatibility with team
• Replicability of work

Possible outcomes:

• Continue
• Redirect
• Remove

Minimal Implementation

For immediate use:

• Assign a real task with constraints
• Require output within 4 hours
• Require documentation
• Evaluate:

 - Was something built?
 - Is it real?
 - Can others replicate it?

Key Constraint

The BEP must remain embedded in real production.

It must not become:

• A theoretical assessment tool
• A personality evaluation system
• A bureaucratic process

It must function as a real-time filter within active build work.

Summary

The BEP evaluates behavior through production.

It is not about what people say or intend.

It is about what they build, how they build it, and whether others can build it again.

Links

• The Behavior Ops Manual