This is a public-safe co-review packet for the next Auzietek publishing pass. The private bkc-channel payload keeps the raw source zips, editorial contracts, issue notes, and working manifests. This page shows the parts that are useful for visual and editorial review without exposing the full private backchannel.

What this packet is trying to fix

The recent public-lane work exposed three repeatable risks:

• articles can become too short when card summaries accidentally shape the body;
• mobile layouts can regress when side rails squeeze the article column;
• media can disappear, break, or become decorative instead of evidentiary.

The next pass should treat those as product-quality problems, not cosmetic preferences.

Editorial contract

The strongest rule from the package is simple:

Cards may summarize. Article bodies may not be silently compressed.

That means a listing card can be tight, but the article itself should preserve the useful explanation, commands, screenshots, warnings, caveats, and historical voice from the source material.

For technical articles, the target shape is closer to a good computing magazine:

1. problem;
2. why it matters;
3. mental model;
4. evidence;
5. implementation;
6. validation;
7. caveats;
8. next step.

When a source article is weak, the fix is not to invent certainty. The fix is to mark the weakness, preserve what is useful, and point to the next real lab or repo step.

Layout contract

The layout package focuses on containment rather than hiding overflow. The important rules are practical:

• use minmax(0, 1fr) for flexible grid tracks;
• give grid and flex children min-width: 0;
• keep article media bounded inside the article body;
• let code blocks and wide tables scroll inside their own frames;
• collapse the right rail before it can crush the article;
• avoid using overflow-x: hidden as the first fix.

That last point matters. If a mobile page is too wide, the correct response is to identify the object that widened it, not simply crop the problem off-screen.

Graphics direction

The graphics package is original SVG work intended to create a consistent visual grammar across Auzietek, Linux Users, Retro Users, and BlackKnightController.

The badges are meant to behave like small trust markers rather than loud decorations:

How this should enter the product

This packet should not be bulk-copied into the public repository. The safer path is:

private bkc-channel payload
  -> select public-safe article or asset changes
  -> update micro-blog content/code
  -> run validation
  -> deploy lab canary
  -> promote beta/public
  -> write receipt

That keeps the collaboration loop flexible while still making the published site clean, reviewable, and defensible.

Review checklist

For this page and the next theme pass, reviewers should look for:

• article body depth versus card summary length;
• mobile article width at 320, 375, 390, and 430 pixels;
• side rails collapsing before content becomes unreadable;
• images staying inside the article body;
• badges adding trust without becoming clutter;
• graphics reinforcing the lane rather than overpowering the text.

The point is not to make the site louder. The point is to make the evidence, the lane identity, and the reader path easier to understand.