They measured me in options. The market measured me in signatures.
“None,” I said, steady as glass.
The word tasted like rust, but I did not blink.
The CTO had just asked me, in front of the entire leadership offsite, what kind of stock package I was sitting on. I told the truth in one syllable, with no emotion at all.
But the silence that followed was louder than any laugh.
He gave me that half-smirk, the kind people reserve for someone who still brings paper maps to a GPS meeting.
“Well,” he said, letting the word hang just long enough for everyone to hear the joke before he even finished it, “let’s fix that discrepancy, huh?”
A few board members chuckled. Someone clinked a glass against a water goblet. A woman from finance looked down at her folder like the carpet had suddenly become fascinating.
And just like that, the room moved on.
People think power announces itself with title slides and leather chairs. But real power is quieter. It clicks shut inside folders. It timestamps emails. It waits.
I slid the beat-up manila folder back into my bag.
Top tab: exhibits, personal.
No one asked.
They never do.
I already knew I was marked.
The new CTO did not even bother hiding it. Fresh from a Series D darling with slick hair and flippant brilliance, he had walked in two months earlier and asked whether our core architecture was “grandma-proof.”
I was the one who built it.
He said it with a grin, like it was a punchline only he found funny.
I logged it, along with everything else.
So when he circled back during the board Q&A and started talking about equity holders driving innovation, I saw the setup before the question left his mouth.
“What about you?” he asked. “What kind of stock package are you sitting on?”
“None,” I said. “Not yet.”
I did not add a complaint. I did not look embarrassed. I did not reach for sympathy. It was simply the truth.
And in that moment, I watched him write me off in real time.
I was not a stakeholder.
I was a placeholder.
The truth was, I had asked for equity twice. Once after our second patent approval. Once after the product hit one hundred thousand users.
Both times, the CFO smiled like I was asking for sprinkles on a filet mignon.
“We can revisit that at the right milestone,” he said.
Then they promoted two men whose biggest contribution had been breaking the CI pipeline for a week straight.
But that was fine.
I was not there to decorate the org chart. I was there to build.
And what I built, I kept receipts on.
What they did not know, what no one in that polished lakeside conference room knew, was that “none” did not mean nothing.
My options were not shares.
They were patents.
Twelve of them.
Quietly filed. Methodically structured. Tied not to the company, but to me.
My name. My clauses. My fallback if I ever became, in their words, redundant.
And I could already feel it happening.
The shift.
The silence when I entered a room.
The way my roadmap presentations got shortened, then skipped.
The way my Slack messages grew colder, like I had caught a professional disease.
The symptoms were all there.
This was not my first layoff dance.
But what they did not understand was that I had been choreographing my own steps.
That day after the Q&A, I went back to my hotel room, locked the door, opened my personal laptop, and pulled up the folder labeled Clean Transfer Drafts.
I scanned the twelve patents, all filed through my own counsel, all housed under my little Delaware LLC.
Benign name. Nothing flashy.
Each patent carried the same escape hatch clause.
License terminates if I am let go without cause. Ownership reverts to me. No approval needed. Just a form and a clock.
The CTO thought he was the only one who understood leverage.
He thought stock was the only kind of stake that mattered.
But stock is a vote.
Patents are a voice.
And mine were about to get very, very loud.
They scheduled the realignment meeting for 4:15 p.m. on a Thursday.
That is how you know it is personal.
Friday layoffs are for spreadsheets. Thursday afternoons are for theater.
I walked in with my laptop, a legal pad, and exactly zero illusions.
The HR director was already in the room. She gave me a pity smile, the kind you give someone who has dropped an ice cream cone.
The in-house counsel sat beside her with a folder aligned perfectly with the table edge.
The CTO, of course, was mysteriously caught in another meeting.
I did not bother asking who else had been cut.
When they call it a realignment, what they mean is, “We pushed you out and gave the guy with the podcast a raise.”
They read from a script, soft and paper-thin.
“This has nothing to do with your performance,” HR said.
Which is corporate code for: this has everything to do with optics.
I nodded.
I even smiled.
I signed their little goodbye letter with the pen I had brought myself, because I do not trust borrowed ink for moments like these.
Then I opened my bag, took out a single envelope, certified mail already prepped, and slid it across the table to the in-house counsel like I was tipping a waiter.
“Per Section Seven,” I said, my voice even, “this constitutes formal notice of license reversion review. You have fourteen days.”
They blinked.
It took a full beat for them to realize I was not talking about the severance agreement.
Counsel reached for the envelope like it was radioactive.
HR just stared.
That was the moment I realized they truly had no idea what they had just stepped on.
It was not ego. I was not the only person in the company with ideas.
But I was the only one who had taken those ideas, diagrammed them, formalized them, filed them, and locked them in language even the CEO’s golfing-buddy lawyer could not unwind in under two weeks.
Then came the box.
Standard issue. Cardboard. Pre-creased, with a white sticker on the side reading Exit Kit.
I think someone in operations thought that made it more humane.
HR gestured to it like it was a warm blanket.
I filled it slowly.
Keyboard.
Mouse.
Two books they never read but always complimented.
I left the team photo on the desk. That was a lie I did not need to carry out the door.
They walked me out through the side exit like a delivery.
No one from engineering looked up except Carl, the junior front-end developer, who mouthed, “What?” as I passed.
I did not answer.
I just kept walking.
Outside, the wind bit sharp and clean. The sky was the kind of clear that feels like an insult.
I put the box in my trunk, sat in the driver’s seat, and stared at the building for a full minute.
Not in mourning.
Not even in anger.
Just logging the moment like a timestamp.
Then I opened my phone and messaged my attorney.
Go time. All twelve.
She replied with a thumbs-up and a single line.
Already drafting transfers to the LLC.
I drove away without music, just the soft thunk of tires over the speed bumps they had installed after one too many late-night accidents.
That building behind me did not own what it thought it did.
Not anymore.
In fourteen days, the licenses they had built entire roadmaps on would revert to me.
They had terminated me with a generic clause and a cardboard box.
What they triggered without even knowing it was a legal countdown.
The patents were about to come home.
The morning after they walked me out, I brewed my coffee slowly.
Not for comfort.
Out of ritual.
Ritual means control. And right then, control was the only currency I still had in surplus.
I did not let myself spiral.
No sad playlists.
No open-ended journal entries.
Just a checklist.
At the top: transfer.
I opened the secured drive and scrolled through the patent titles, each one like a scar I had earned the hard way.
Twelve total.
Eleven methods. One system architecture.
Filed over three years, independently, surgically, obsessively documented, all assigned to me under provisional license agreements tied to my employment with one very specific clause built into each.
Upon termination without cause, primary rights revert in full within fourteen business days.
No appeal.
No renegotiation.
Just a clean snap.
My LLC, Parallax Formations, registered in Delaware and masked through a trustee for privacy, was always the fallback.
A simple little container, like a fireproof safe no one knew was sitting beneath the floorboards.
At 9:47 a.m., I opened the template transfer forms.
At 10:06, every single one was signed and timestamped.
The filings auto-forwarded to my attorney, who initiated the change of record with the USPTO.
Control consolidated.
Ownership moved.
Just like that.
Next came notifications.
You learn quickly in this game that silence is not protection. It is negligence.
So I drafted notice emails to all prior licensees.
Not many.
A few third-party partners. A couple of enterprise clients who had negotiated limited-use clauses tied to shared projects.
I kept each email polite, clean, surgical.
Dear Name,
Please be advised that as of date, primary ownership and licensing authority for patents listed has transferred from company to Parallax Formations LLC. All active agreements remain in place under their existing terms, pending standard review under reversion clauses. For new licensing or renewal discussions, please contact licensing@parallaxformations.com.
Respectfully,
My full name.
That email signature hit differently now.
Then I changed the autoresponder on my personal site.
Before, it had been a standard thanks-for-reaching-out message.
Now it read:
For all patent, licensing, partnership, or technical inquiries, please contact licensing@parallaxformations.com. This email is no longer affiliated with company.
No drama.
Just a wall drawn in fine permanent ink.
By 2 p.m., my inbox was already stirring.
A licensing officer from a regional platform asked if the reversion applied to the UI compression method they had embedded.
It did.
A compliance lead from a medical SaaS startup I barely remembered sent a confused question.
Wait, do we owe someone else now?
I replied once, short and friendly, then forwarded the rest to my counsel.
Meanwhile, my old company had not even flinched.
No LinkedIn updates. No internal bulletins. No quiet memo to product leads.
They still thought they had removed a name from a payroll line.
What they had done was trigger a review window across their entire product suite.
The architecture they built had been modular by my choice.
Easier to license.
Easier to unhook.
Every time I clicked send, I felt something uncoil.
Grief did not get a seat at this table.
It showed up, sure, knocking with its usual speeches about loyalty and wasted time.
But I was too busy sending certified PDFs to let it in.
The chessboard had tilted.
And for once, I was not the pawn.
I was the rule they had forgotten existed.
Twelve pieces.
One board.
Check had just been announced.
I did not want to build a shrine.
I wanted to build a mirror.
Something so clean, so undeniable, that when people looked at it, they would have no choice but to see whose fingerprints were all over the work.
So I built the library.
No branding. No fluff. Just code.
Modular. Elegant. Deeply annotated.
Every method, every system architecture component, rewritten from scratch based on the same foundational principles as the patents now housed under Parallax.
I used clear file names, simple API calls, and most importantly, documentation that actually taught instead of merely listing.
My old company used to bury logic in business jargon.
I stripped that out like rot.
By week’s end, it was live on GitLab under a fair-use license.
MIT-inspired, but with one clause that could not be overlooked.
Attribution must be visible to end users in either the footer, about panel, or equivalent persistent element. Removal or obfuscation constitutes license termination.
I did not bury it in fine print.
It was line three.
You could not miss it unless you were trying to.
And anyone who did try would hit the failsafe.
A single test method in the shared repo checked for attribution. Fail it, and your build would throw a quiet warning flag. QA engineers would catch it before it ever made it to production.
I made sure of it.
The library itself, I called Plainform, a nod to what the original platform was supposed to be before marketing got hold of it.
I spent four straight nights getting it right.
Not perfect.
Bulletproof.
Function first. Human-readable.
The kind of tool I would have given anything for ten years earlier, when I was still debugging 3 a.m. builds alone.
I did not announce it.
I just pushed it and pinged three open-source developers I respected, none of whom had any ties to my old company.
Within forty-eight hours, one of them forked it and posted, “This library feels like someone finally read the manuals we never got.”
That was the first crack.
The second came when a small Canadian fintech app quietly pushed a beta with Plainform modules embedded.
In their about panel, it read:
Powered in part by Plainform. Attribution: my name, Parallax Formations.
Clean.
Respectful.
Legal.
Effective.
Because what I had built worked better than what I left behind.
Faster render times. Lighter load. And unlike my former employer’s tangled pile of internal compromises, this was a blueprint anyone could follow.
I wanted it that way.
I did not care who used it.
I cared that they gave credit where credit was due.
Over the next few days, clones and stars ticked up.
Not viral.
Persistent.
Steady.
The way reputation actually spreads through usefulness, not noise.
Some of the forks added tweaks and modules.
Fine by me.
That was the point.
But every single one, thanks to that one immovable license clause, carried my name somewhere small, somewhere quiet, where end users could see it.
It was not revenge.
It was not glory.
It was infrastructure.
And infrastructure does not beg to be noticed.
It simply refuses to be ignored.
My old company had gatekept for years, treating architecture like a kingdom, hoarding access and stamping every page with their watermark.
I built a road, paved it smooth, lined it with working lights, and at the end of it, I left a single sign.
Plainform by my name.
Attribution required.
They built walls.
I left the door open.
And the market knew how to walk through.
The first time I saw it, I laughed so hard I had to set my coffee down.
A screenshot, grainy but clear, was circulating in a developer Slack I still had eyes on through an old side email.
It was a beta release from Rindle, one of our loudest competitors.
Their shiny new UI was sleek as ever.
And down at the very bottom, right where your eye lands just before you close the tab, sat the line:
Powered by my name, licensed via Plainform.
Gray text.
Small, but not small enough.
They had not customized it.
Not even a little.
That told me two things.
One, they were moving fast.
Two, they did not have time to build their own system.
That meant urgency.
That meant adoption.
That meant momentum was already slipping from the hands of the people who had fired me and moving straight into mine.
By the end of the week, the repo had 470 stars and 112 forks.
Ten separate threads opened with titles like Integration Tips and Best Practices for Attribution Placement.
The second one made me laugh.
It used the exact language I had proposed in our product design review six months earlier, the one the CTO dismissed with a casual, “That’s too academic.”
Now developers were copying it into production with the reverence of gospel.
The irony was thick enough to spread on toast.
I lurked through the issue threads and watched names I recognized, including people who had never responded to my DMs, debate performance deltas and config options like I had not spent the last year begging for a build freeze to fix that very thing.
They were quoting me verbatim without knowing it.
My old diagrams, stripped of logos, were being ported into Notion docs and Figma boards at startups I had never spoken to.
It was like watching ghosts reenact your past life.
Only this time, you were not being talked over.
One thread in particular stayed with me.
A DevOps engineer from a Brazilian analytics firm wrote, “Finally, someone documented this the way real engineers think.”
He did not know who I was.
He did not care.
But that comment hit harder than any peer review I ever got from my old team.
Meanwhile, back at my former employer, the silence was deafening.
No counter-release.
No smug Medium post.
Not even a bug-fix announcement.
That told me exactly what I needed to know.
They saw it.
And they did not have an answer.
Because here is the truth: most companies are not agile.
They are scared.
Scared of moving too fast, too loud, too far from the plan.
I was no longer their plan.
And now the plan was slipping away.
I got a ping from a recruiter at a firm that used to poach from us like vultures.
The message was polite.
Friendly, too friendly.
We’re exploring some integrations and noticed your name on quite a few builds. Would love to connect.
Translation: You have leverage now. Can we buy it off you?
I declined.
This was not about cash.
Not anymore.
It was about visibility.
That attribution line, silent, humble, low-resolution, was doing the work of a thousand résumés.
Not just in one app.
Not even in one market.
Everywhere.
Healthtech. Education platforms. Even a climate data nonprofit had dropped Plainform into its mobile site and included my name in the onboarding splash screen.
The CTO once told me, “Real architecture is invisible.”
I used to believe him, until I realized invisibility was just what people like him relied on to take credit quietly.
Not anymore.
My work was visible now.
In footers.
In menus.
In metadata.
And for once, no one could talk over it.
No one could push it into a Jira backlog and forget it existed.
They built a system to forget me.
I built one that remembered itself.
They thought they could sneak it in.
Two weeks after Plainform started showing up in competitor betas, I caught wind that my old company, Vyrex, had quietly folded sections of it into their new modular rewrite.
No press.
No change-log mentions.
Just buried commits with obfuscated variable names and my attribution line stripped clean.
They did not even fork it.
They copied it.
Whole files, line for line.
Then they did what they always did.
They rewrote just enough to pretend it was original.
But code has fingerprints.
Logic has rhythm.
QA has rules.
I would not have even noticed if not for an anonymous pull request on the Plainform repo.
Someone asked whether the core modules were meant to throw a fail flag when attribution was missing.
The language was careful.
Too careful.
I traced the user to an IP block linked to Vyrex’s offshore QA partner.
Sloppy.
Turns out my license checker did exactly what I built it to do.
When they tried to integrate the stripped version into their build pipeline, the validator tripped.
Internal QA flagged it.
Because even outside companies know what their own risk profile looks like.
And this was not merely risk.
It was misappropriation wearing a trench coat made of arrogance.
The internal scramble must have been magnificent.
A day later, a former engineering manager, one of the decent ones, texted me a single screenshot.
An internal Slack message from their QA lead.
Blocking launch. License non-compliance. Attribution clause hit.
No emoji.
No reaction.
Just a hard stop.
The next blow came quieter but deeper.
Their largest enterprise client paused renewal.
Not canceled.
Not yet.
Just seeking clarification on IP integrity.
A polite way of saying: prove this is yours, or we walk.
Then came the pressure point.
Their liability insurer sent a formal request.
Please confirm current patent ownership and active licensing rights for components listed in Appendix B. Documentation must be delivered within 48 hours to maintain coverage.
Appendix B was nearly all mine.
No response meant policy lapse.
Without coverage, Vyrex could not ship.
Their CTO could swagger all he wanted on earnings calls.
But without insurance, one serious IP claim could crater their release schedule.
Suddenly, I was not just a former employee.
I was the only person who could put out the fire they had lit.
But I did not gloat.
I did not send a taunting email.
I did not schedule a smug Zoom.
I waited.
I kept every email, every timestamp, every commit hash.
My folders were clean.
My records were airtight.
This was not revenge.
It was bookkeeping.
The last thing they expected from me was quiet control.
That was why it worked.
While they panicked in boardrooms and passed around redacted PDFs, I did nothing.
I refreshed my inbox, watched the clock, and let the squeeze do its work.
Because you cannot run fast and hide footprints at the same time.
The second they tried to erase me, they stopped moving forward.
That is what happens when your innovation depends on a name you tried to delete.
Turns out, stripping attribution strips more than a footer.
It strips stability.
It strips coverage.
It strips trust.
And all I had to do was let the license do what licenses do.
The email came in at 6:12 a.m.
Subject line: Request for urgent discussion — IP clarification.
No greeting.
Just a meeting link and a block of names that looked like someone had dumped the entire Vyrex leadership tree into Outlook and hit send.
The kind of list you only use when legal is pacing and someone in finance is whispering the word exposure.
I poured my coffee.
I took my time.
At 6:27, I clicked the link.
Seven faces stared back at me, puffy-eyed, overcaffeinated, and trying too hard not to look desperate.
The CTO was there, of course, jaw set like he was chewing gravel.
Legal.
Compliance.
An insurance liaison.
Two board members I had not seen since the last roadmap review they ignored.
“Thank you for joining,” Legal started.
Too polite.
“We’re hoping to resolve a few licensing questions directly.”
I let the silence stretch until it got awkward.
Then I said, “Sure. Let’s talk terms.”
They danced around it at first, hiding behind language.
Harmonization of assets.
Long-term alignment.
Mutual predictability.
I have seen toddlers negotiate with more grace.
Eventually, one of the board members, Conrad, cut through the fog.
“Look,” he said, “we’d like to discuss an exclusive relicensing agreement. Something that protects both parties and restores predictability, with attribution optional.”
I did not laugh.
I did not blink.
I opened the folder on my desktop and double-clicked the PDF labeled Gatekeeper — Sheet Final.
One page.
No fluff.
Just lines.
Cross-license agreement offer.
Non-exclusive access to patents listed for internal and commercial use.
Attribution mandatory in visible footer or about screen.
Unmodifiable backdated royalty structure starting from termination date.
Audit rights retained by licensor.
Agreement non-transferable without prior approval.
Term perpetual unless terminated by violation.
I screen-shared it.
I let them read it.
I let them choke on the simplicity.
The CTO leaned forward.
“We’re offering exclusivity.”
I shook my head.
“You don’t have that kind of leverage anymore. The market’s already moved. Rindle is shipping with my footer. So is Yarrow. So is LeapSpan. The industry chose attribution over erasure. I’m just formalizing it.”
He bristled.
“We can negotiate that clause.”
“No,” I said. “You had your chance to negotiate before you stripped the attribution and triggered a coverage review. This isn’t a takedown. It’s a toll booth.”
The insurance rep unmuted, voice strained.
“We’d recommend signing her offer as is.”
There it was.
The moment.
I was not the problem anymore.
I was the solution they could not launch without.
The CFO, silent until then, finally spoke.
“Are you open to revisiting rates down the line?”
I shrugged.
“Sure. If your volume justifies it. But right now, you’re two weeks into backdated royalties and seven days from a full policy lapse. This is the bridge. Walk it or don’t.”
They all stared at the screen.
That one-page PDF glowed like scripture.
I muted myself and let them sit in it.
This was not vengeance.
I did not need to crush them.
I just needed them to say it out loud, even if they never used the words.
We need you.
We see you.
You built this.
And now, if they wanted to keep building, they would have to pay the toll.
Footnote included.
Revenue froze before the frostbite registered.
Three of Vyrex’s biggest accounts, all legacy clients, flagged their Q4 renewals for review.
No escalation.
No tantrums.
Just polite corporate dread disguised as delay.
That was what made it dangerous.
Nobody panics when a client yells.
But when they go quiet, that is blood in the water.
Meanwhile, LeapSpan launched its public beta on Product Hunt.
Smooth. Snappy. Loaded with performance benchmarks Vyrex used to brag about before they gutted the team that made them possible.
And there it was, clear as daylight in the about panel:
Powered in part by Plainform. Attribution: my name, Parallax Formations LLC.
Small.
Gray.
Unmissable.
The same week, Rindle pushed a major update and added a new section to its investor deck.
Infrastructure stability through open licensing.
Slide six.
Screenshots with my name at the bottom of two modules.
Vyrex’s board did not need a pie chart to connect the dots.
Competitors were shipping.
Clients were stalling.
Legal was sweating.
And the PDF I sent was still unsigned, still sitting in someone’s review folder while their internal compliance logs quietly filled with red flags.
Internally, they called it “the gap.”
The window between when their last deploy was rolled back and when the next one could pass QA.
But nobody wanted to admit what it really was.
A vacuum.
Of leadership.
Of architecture.
Of options.
I heard from someone on the inside, anonymously through a back channel, that engineering was throttled.
Features were finished but could not be released.
Not without risking exposure.
Not without license coverage.
Not without me.
And now investors were asking questions.
The kind with teeth.
Why does your competitor’s footer have her name?
Is your IP defensible?
Why did you remove the attribution clause?
On a Friday afternoon call, the CTO tried to save face.
“We’re negotiating. We won’t be strong-armed into permanent credit lines just because—”
That was when counsel cut in.
Quiet voice.
No camera.
Just audio, like a ghost in the room.
“We have to sign her paper.”
Three seconds of dead silence.
And just like that, the room shifted.
Not outwardly.
Internally.
You could feel it like pressure dropping before a storm.
Everyone saw what it meant.
The debate was over.
Not because they agreed.
Because the math had turned.
Attrition over attribution was no longer a strategy.
It was a loss.
I did not celebrate.
I did not crack a grin or pour a drink or send a smirking emoji to anyone.
I opened the PDF again, made sure the date still aligned, and left it untouched.
No edits.
No sweeteners.
No ego.
Because what mattered was not the signature.
It was the shift.
The tremor that had lived in my hands for months, the one that started the day they boxed up my desk, had stopped.
Not because they apologized.
Because they could not move without me.
They thought they had written me out.
Turns out, I was the code that would not compile without attribution.
And now they knew it, too.
The official investor update was scheduled for ten.
But I knew they would start late.
These things always do.
Too many suits trying to squeeze optimism into a quarterly slide deck padded with half-finished roadmaps and delays framed as pivots.
I did not dial in.
I did not need to.
Word would find its way to me eventually.
And it did.
At 10:47 on the dot, through a forwarded transcript from someone who still believed in right and wrong, the line arrived halfway through the call.
Quiet, but unmistakable.
No dramatic pause.
No forced apology.
“She owns the claims,” counsel said.
Three words.
Dry.
Clinical.
Devastating.
You could feel the recalibration ripple through the audio.
Projected revenue forecasts crumbled in the background. Shareholder optimism deflated behind practiced smiles.
The CTO did not speak.
He could not.
Not after doubling down for weeks on containment.
Not after the insurers demanded proof and got silence.
I had already countersigned the agreement hours earlier.
My terms did not change.
Non-exclusive cross-license.
Attribution permanent, visible, non-negotiable.
Royalties backdated to my termination date.
Audit rights for all current and future builds.
It was not revenge.
It was clarity.
They submitted to the same license as everyone else.
No back doors.
No exclusivity.
No sweetheart redlines.
Just the cold logic of legal cause and consequence.
The same people who had laughed when I said I had no stock were now looping in legal to analyze every word of my clauses.
I did not have options.
I had ownership.
Later that day, the update email hit my inbox.
A mass announcement from Vyrex’s communications team.
Spin, as expected.
Excited to partner with independent creators.
Strengthening our IP foundation.
Not a single mention of my name.
But the attachment told the real story.
Plainform license terms.
Signed.
Effective immediately.
I did not respond.
I did not share it.
I archived the message and got on with my day.
Around sunset, I took the long way home.
It was not intentional.
Muscle memory, maybe.
My car crept up to that stretch of office parks I used to know so well.
The old building came into view, still sterile, still lifeless.
I did not look up.
I did not slow down.
I just rolled past the parking lot where I had once spent ten minutes crying into a steering wheel the day they took credit for my build.
At home, I kicked off my shoes, grabbed a drink, and opened my tablet.
Three apps.
Competitors.
Former allies.
Upstarts.
All shipping features powered by Plainform.
I tapped through the menus and scrolled to the footers.
There it was.
Powered by Plainform.
Attribution: my name, Parallax Formations.
On one app, it was in a footer bar.
On another, tucked into the about screen.
On the third, proudly center-aligned in the credits page, right above the development team.
Small.
Permanent.
Unavoidable.
That is the thing about ownership.
It does not ask for applause.
It waits until the people who dismissed you have no choice but to cite you.
Until the story they tried to rewrite ends up with your name at the bottom of every page.
They measured me in options.
The market measured me in signatures.