Portfolio presentation on projectious.work brand

Status treatments

Mon, 01 Jan 0001 00:00:00 +0000

Required pattern

Every project presentation must show a status as text. Color, icons, position, and motion may reinforce the label but must never replace it.

Status	Use when	Supporting cue
Usable project	Documented users can complete the stated core task.	Solid dot
Working prototype	A real implementation runs, with known limits.	Half-filled dot
Applied research	Evidence or experiments are the primary output.	Diamond
Supporting asset	The repository enables another project.	Square
Idea / implementation starting	Scope exists; implementation is absent or partial.	Ring
Archived	Work is preserved but no longer maintained.	Horizontal bar

Do not substitute broad claims such as “platform”, “production-ready”, or “enterprise” unless the owning repository publishes evidence for that claim. Prefer narrow artifact categories: CLI, process layer, applied research, prototype, library, or supporting asset.

Social previews

Mon, 01 Jan 0001 00:00:00 +0000

Content model

Every 1280×640 preview contains only:

Projectious organization mark and name.
Project name.
One narrow artifact category.
One complete maturity label from the status vocabulary.
An optional short limitation, never a marketing claim.

The editable source is brand/portfolio/social-preview-template.svg. Replace bracketed text, keep the status label intact, and save a project-specific SVG beside the template. Examples for aibox, processkit, ai-market-research, and KubeClaw demonstrate the content structure; they are not evidence of current maturity.

Diagrams and demos

Mon, 01 Jan 0001 00:00:00 +0000

Architecture and flow diagrams

Prefer left-to-right flow, explicit boundaries, and named protocols.
Distinguish implemented components from planned components with text: implemented, external, or planned.
Add a caption with repository, source path, commit or release, and capture date.
Never infer architecture from a social preview or marketing page.
Keep editable source beside the export and document the export command.

Suggested caption:

Source: owner/repository, docs/architecture.svg, release vX.Y.Z, captured YYYY-MM-DD. Planned elements are labelled.

Documents

Mon, 01 Jan 0001 00:00:00 +0000

A document is not a screen that happens to be printed. It has a fixed page box, no hover state, no dark mode, and one shot at being legible on a printer nobody tested. This page defines the pattern the system uses for short, laid-out documents, and links the worked example.

	Source
Resume / CV	`brand/examples/resume.dc.html`

Longer, flowing documents — reports and papers — use the LaTeX and Typst templates in brand/templates/ instead. The split is about pagination, not length; see below.