Showing it to someone

You have a repository, a URL, documentation and a certificate. Now you need the sentences that go with them.

Lead with the decisions, not the features

A list of features is a screenshot with extra steps. What distinguishes your artefact is the decisions, and they are more interesting than any of the features:

"The API key never reaches the browser — everything goes through a server proxy, and CI fails the build if the key is referenced outside it. The cockpit shows the age of every panel because a multi-symbol response carries different timestamps per row. The backtester's tests check that changing future bars cannot change a past signal."

Anyone can generate a dashboard. Very few can say why theirs shows a timestamp per panel, and that sentence is the one that lands.

Say what it cannot do, early

Counterintuitive and reliable: naming a limitation raises credibility rather than lowering it.

"Alerts only run while the page is open, because a real alert loop needs 936 calls a day and the free tier allows 20."

That sentence proves you measured, understood the constraint, and made a deliberate choice. A person who says only what their project does has told you nothing about whether they understand it.

Show the review, not just the result

Your REVIEW.md, your test names, your CI. The test called "changing future bars must not change a past signal" is a better signal of seniority than any feature, because it shows you know where this domain lies to you.

The certificate is evidence, not the claim

It says you passed an exam about bias detection, cost arithmetic and secret handling. That is real and worth listing.

It is not the interesting part. The interesting part is the repository, and the certificate's job is to make someone open it.

Answer the honest question

Someone will ask whether the AI wrote it. The truthful answer is the strong one:

"Yes, a lot of it. I planned it, reviewed every diff, and I can tell you which parts I rejected and why. The first version put the key in the browser and the second had an N+1 that cost 400 calls a page."

That answer demonstrates exactly the skill this track teaches: knowing what to accept.

Try it now

Write the three-sentence description and read it aloud. If it is a list of features, rewrite it as decisions. Then send the repository to one person who will actually look, because an artefact nobody has seen is not yet finished.