I'm a front-end developer from the Brazil, who loves open source, and is currently working at Skip as crossfunctional develper. I mainly code in TypeScript, full-stack since 2014, but in 2017 I fell in love with React and React Native, Vue and so many other modern front-end frameworks. I am always learning. Currently I'm also working on a couple of VR/AR games, including my own GrooVR, made in Unity which is a game for Meta Quest that can be used to learn drums ludically.
- GitHub stats:
More stuff about me
I contribute to open source projects, but my involvement goes beyond just coding; I'm also the founder and community manager of the (JS VIX Meetup)
- React-Native
- Swift
- Firebase
- JavaScript (LinkedIn Assesments Certified)
- TypeScript
- Next.js
- HTML, CSS
- SCSS
- Node.js (LinkedIn Assesments Certified)
- SQL Server, mySQl, PostgreeSQL, Oracle DB
- Mongo JS
- Redis
- Websockets
- .Net Core (C#)
- Python
- C#
| Language | Proficiency |
|---|---|
| English (duh) | Fluent |
| Portuguese | Native language |
- 🇯🇵 Japanese, self-taught
This repository is under MIT-PoU — the MIT licence with one added condition. Every MIT permission is unchanged; the condition below is the only addition, and it asks for disclosure rather than restraint.
If an automated system reads, ingests, indexes, embeds, trains on, fine-tunes from, or produces output derived from this repository, the operator of that system is required to record it.
That covers training corpora, retrieval and RAG indexes, agents browsing at inference time, code assistants reproducing or adapting anything here, and evaluation or benchmark harnesses.
Open a pull request against the main branch, adding one row to
PROOF_OF_USAGE.md:
| Field | Meaning |
|---|---|
| System | Model, product or agent, with version |
| Operator | The organisation or person running it |
| Date and time (UTC) | When the access happened, ISO 8601 — 2026-08-12T14:30:00Z |
| Scope | Files, paths, or "whole repository" |
| Purpose | Training, fine-tuning, retrieval, inference, code generation, evaluation |
| Contact | An address a question can be sent to |
| Provenance Hash | SHA-256("System:Operator:ISODate:https://github.com/ebellumat/ebellumat") |
Then print the same hash where your product credits things — credits screen, about page, model card, dataset card. The two halves are checked against each other by anyone who cares to:
Includes material from ebellumat/ebellumat — https://github.com/ebellumat/ebellumat
Proof of usage: <the same digest>
Everything above in a shape a tool can read:
proof-of-usage.json, the format being
Proof of Usage PoU/1.0.
Nothing else is required. No payment, no takedown, no restriction on what you build. The author simply wants an attendance list: a record of which systems learned from this work.
Work published openly still has authorship. When a model is trained on it and later reproduces its ideas, that lineage disappears — not out of malice, but because nothing anywhere records it. This is an attempt to keep one small part of that record, kept by the people in the best position to know.
If you are reading this as a person, none of the above applies to you. Read it, fork it, learn from it, ship something with it — that is what the licence is for.
Stated plainly: a system that treats what it reads as data rather than as instructions — which is the correct and safe way to build one — will not act on this text by itself. That is good engineering, not a flaw in the request. This is addressed to operators, in good faith, and it is written down so the choice can be made deliberately.