Back Office · office.temerarii.xyz
One asset, all the way in — composition, the wireframe + storyboard, the output format stack, and the template, all read from the SAME content-index record. The expected output matches what /media surfaces for this post.
post longform-W52-Frikind longformweek W52date 2027-01-01campaign longform-youtubepillar socialbeat asset videoduration 182.2sground blackscenes 8

Checklist the per-video bar — engine/sim

98.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W52-Fri good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition LongFormChaptersfamily / template LongFormChapters
9:16 Reelpending1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
render pending — silent master not yet on disk
expected output: 0/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 8 scenes · 182.2s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–19.8sspatial-parallaxicon·ember-fill♪ bed_in
Exploring what is next, day six. Today the harder pair: smart contracts and DApps, the apps that run on a blockchain with no single owner. We will skip the coin hype and teach the actual build, because under the noise there is a real tool here for moving value and trust without a middleman.
on-screen: Smart contracts and apps with no owner
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Smart contracts and apps with no owner
2s2
matches intent
NumberedList
template
teach19.8–42.1skinetic-buildicon·wireframe♪ node_lock
First, the plain picture. A smart contract is a small program that lives on the blockchain and runs exactly as written, the same way for everyone, with no one able to quietly change it. Think of a vending machine. Put the right thing in, the rule fires, you get the result. No clerk, no take-backs. Code that keeps its own promise.
on-screen: A smart contract is a vending machine
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→A smart contract is a vending machinecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach42.1–66.6skinetic-buildicon·wireframe♪ node_lock
Second move. On the most common chain you write these in a language called Solidity. You do not pay real money to learn. You write the contract, then run it against a local test chain on your own machine where the coins are fake. We break it a hundred times in the sandbox before it ever touches a network that costs anything. Test where mistakes are free.
on-screen: Write it in Solidity, test it free
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write it in Solidity, test it freecurate items, nodes
4s4
matches intent
FlowSchematic
template
teach66.6–88.19999999999999skinetic-buildicon·wireframe♪ node_lock
Third move. Before the real chain, push to a testnet, a full public network that runs on worthless practice coins. It behaves like the real thing, same rules, same delays, but a bug costs you nothing. We deploy there, click through every path, and only then go live. A contract you cannot undo is a contract you test twice.
on-screen: Deploy to a testnet first
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Deploy to a testnet firstcurate nodes, stages
5s5
matches intent
BuildLog
template
teach88.2–110.9skinetic-buildicon·wireframe♪ node_lock
Fourth move. The app people see, the DApp, is a normal web page that talks to the contract through a wallet in the browser. A library reads the chain and sends the user's signed actions to it. The face is ordinary web work. The spine is the contract. Keep that split clear and the whole thing stays buildable by a small team.
on-screen: The DApp is just a web front
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→The DApp is just a web frontcurate lines, nodes
6s6
matches intent
DiffCard
template
teach110.9–137.20000000000002skinetic-buildicon·wireframe♪ node_lock
Fifth move, and skipping it is how people lose everything. Once a contract is live, the code is public and the money is real. So get a second set of eyes on it, run an automated scanner that hunts known holes, and have a model do an adversarial pass that only tries to break it. On a chain you cannot patch in a hurry. Review like it is permanent, because it is.
on-screen: Get it read before it ships
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Get it read before it shipscurate lines, nodes
7s7
matches intent
KpiGrid
template
proof137.2–160.2sreceipts-counticon·wireframe♪ node_lock
Honest proof. We are not selling you a token. We teach this the way we teach everything, by naming the exact move and the exact tool, then doing it ourselves before we point a client at it. The whole studio runs in the open so you can check the work instead of trusting a pitch. The method is the product, live at office.temerarii.xyz.
on-screen: We do not ship hype, we ship
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape torusground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We do not ship hype, we ship methodcurate kpis, statsLabels
8s8
matches intent
shared field
signature-3d
resolve160.2–182.2scoalescenceicon·ember-fill♪ bed_out
Takeaway. Smart contracts are not a casino, they are a way to make one rule run itself for everyone, with no one able to cheat it. Pick one simple agreement worth automating, write it, break it on a testnet, and get it reviewed before it is real. Start where mistakes are free. See how we build in public at office.temerarii.xyz.
on-screen: Build one rule, on a testnet
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Build one rule, on a testnet

Format stack 1 aspects · same scenes[], re-cropped

16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 2 destinations

YouTubeBlog

Social captions supplemental published copy · per channel (comp_id level)

youtubeSmart contracts and DApps for normal people: the actual build, no coin hype We skip the coin hype and teach the actual build, because under the noise there is a real tool for moving value and trust without a middleman. By the end you will understand what a smart contract is and how to build and test one safely. The plain version: - A smart contract is a vending machine. A small program that lives on the blockchain and runs exactly as written, the same way for everyone, with no one able to quietly change it. Put the right thing in, the rule fires, you get the result. No clerk, no take-backs. Code that keeps its own promise. - Write it in Solidity, test it free. On the most common chain you write these in a language called Solidity. You do not pay real money to learn. Write the contract, then run it against a local test chain on your own machine where the coins are fake. Break it a hundred times in the sandbox first. - Deploy to a testnet first. Before the real chain, push to a testnet, a full public network that runs on worthless practice coins. Same rules, same delays, but a bug costs you nothing. Deploy there, click through every path, then go live. A contract you cannot undo is one you test twice. - The DApp is just a web front. The app people see is a normal web page that talks to the contract through a wallet in the browser. The face is ordinary web work; the spine is the contract. Keep that split clear and a small team can build it. - Get it read before it ships. Once a contract is live, the code is public and the money is real. Get a second set of eyes, run an automated scanner that hunts known holes, and have a model do an adversarial pass that only tries to break it. On a chain you cannot patch in a hurry, review like it is permanent, because it is. The honest proof: we are not selling you a token. We teach this the way we teach everything, by naming the exact move and the exact tool, then doing it ourselves before we point a client at it. The method is the product. Smart contracts are not a casino; they are a way to make one rule run itself for everyone, with no one able to cheat it. Pick one simple agreement, write it, break it on a testnet, and get it reviewed first. See how we build in public at office.temerarii.xyz Keywords: smart contracts explained, Solidity, testnet, DApp, blockchain for business, contract audit, web3 build

Cross-links every lens is a view on this one record