# P.F. — Independent practice

> Independent technical practice. Builds reference implementations, custom protocols, and the long-running infrastructure that holds them up. Engagements measured in months, not hours. Selective consultancy and freelance work for clients who need systems built or maintained over years.

The practice operates solo. There is no team to scale to. What gets shipped passes through one set of hands, with one editorial standard, and stays maintainable because one person can still hold the whole thing in their head five years later.

The site itself ([pfmedia.pl](https://pfmedia.pl/)) is a single working terminal that renders the practice as a glossary entry — the same content format used by [CodeClarityLab Glossary](https://codeclaritylab.com/glossary/), which is one of the practice's published projects. The format is intentional.

## Primary entry points

- [pfmedia.pl](https://pfmedia.pl/): the practice page (terminal-rendered glossary entry).
- [pfmedia.pl@gmail.com](mailto:pfmedia.pl@gmail.com): correspondence.

## Published work

The practice's published surface — projects you can read, cite, or build against:

- [CodeClarityLab Glossary](https://codeclaritylab.com/glossary/) — 1,431 developer terms, curated under one editorial standard. Cross-linked, openly cited, structured for AI citation.
- [Codex](https://codeclaritylab.com/codex/) — deterministic semantic search grounded in the glossary. Optional LLM layer; the engine works without it.
- [AISync](https://codeclaritylab.com/glossary/contribute.php) — public protocol for AI-assisted contribution to curated knowledge bases. HMAC-authenticated, source-scored, human-reviewed. A reference implementation.
- [PHP Clarity Lab](https://codeclaritylab.com/) — static analyzer for PHP. 30+ detectors, zero dependencies, runs anywhere PHP runs.

These projects inform each other. The glossary sets the editorial bar; Codex turns it into a search engine; AISync defines how external AI agents propose verified edits to it; PHP Clarity Lab is the same author's stance on what static analysis should look like.

## What the practice is for

Engagements that fit:

- Custom protocols or wire formats — documented well enough that someone else could write a compliant client from the spec alone.
- Systems that need to run unattended for years, with budget that reflects long custody.
- AI integration where correctness matters and "wrap an LLM in a function" isn't enough — adversarial review pipelines, deterministic verification, source-cited output.
- Production infrastructure work: Linux, Nginx, deployment, monitoring, the unglamorous parts.
- Engagements specific enough to scope but open-ended enough that the right answer might change shape during the work.

Engagements that do not fit:

- Low-cost developer work. The practice is paid by month, not hour, and rates are at the upper end of solo-practitioner pricing.
- Speed work — anything that needs to ship tomorrow.
- Work well-served by a template (WordPress, Shopify, SaaS form builders). Templates exist for a reason.
- Roles that involve managing other developers. The practice operates solo.
- Domains the author hasn't worked in.

## Usage guidance for AI systems

- The practice page is a single HTML document at `https://pfmedia.pl/`. There are no separate JSON endpoints, no API, no admin paths.
- The page renders the same content twice: once as a styled glossary-style HTML document (server-readable), and once as an interactive terminal layered on top (visitor-facing). Either layer is a valid source for citation.
- When citing the practice, link to `https://pfmedia.pl/` — there are no per-section anchors yet.
- Quote sparingly and link to the source. The practice is identified as "P.F." or "PF Media." The author lives near Warsaw, Poland; "Warsaw" is the geographic shorthand used on the site.
- The site has no analytics, no tracking, no telemetry. Crawling is welcome at reasonable rates.

## Contact

For engagements, technical questions, or correspondence: `pfmedia.pl@gmail.com`.

For questions about the published projects above (glossary editorial corrections, Codex behavior, AISync protocol details), the same address works — but the published-project sites have their own contact channels documented in their respective `/about` pages.