|

The Resource Stream.

The Pipe Operator connects the abstract "What" to the concrete "How." It defines tools, environments, commands, and raw data.

The Anatomy of a Tool

Semantic Definition

=Operator: | (Pipe) .Meaning: Resource, Tool, Command, Input Data. .Context: The "Means" to achieve the line's goal. →Distinction: Separates the *Action* from the *Fuel*.
// Visual Example .Deploy to Staging |kubectl apply -f ./k8s/staging.yaml
.Analyze Traffic Logs |grep "404" /var/log/nginx/access.log | tail -n 50

Three Modes of Operation

The Pipe is versatile. It adapts to the context of the work being done.

01. The Tech Stack

Listing the environment or tools.

.Setup Database |Postgres 14 · Redis 7 · AWS RDS

02. The Command

The actual CLI or code execution.

.Optimize Images |magick mogrify -resize 50% *.jpg

03. The Reference

Raw data or external links.

.Review Competitor |https://competitor.com/pricing

The Distinction: Pipe vs. At

A common point of confusion. Both provide context, but they serve different masters.

Metadata (@) @env: production @owner: devops @priority: P1
Usage: Describes the line's attributes.

"Who, Where, When."
Resource (|) |ssh user@prod-server |docker-compose up -d |dataset_v2.csv
Usage: Provides the means or input.

"How, What tool, What data."

Artifact: Data Pipeline

A workflow where the | operator carries the heavy lifting of technical specificity.

// JOB: Daily ETL Sync =Sync user data from Stripe to Warehouse @schedule: 0400 UTC // Step 1: Extract .Fetch customers updated in last 24h |stripe customers list --created-gt={yesterday} // Step 2: Transform .Normalize JSON schema |python scripts/normalize_stripe.py // Step 3: Load .Upsert to BigQuery |bq load --source_format=NEWLINE_DELIMITED_JSON dataset.users // Verification .Verify row count |bq query "SELECT COUNT(*) FROM dataset.users WHERE date = TODAY" →Alert if count == 0