GitHub engineering profile
Public repositories and case-study work show implementation practice across AI systems, landing repairs, education tooling, validation scripts, and technical documentation.
Open GitHub profilePublic proof of work
Recent SecuredMe work, not generic promises.
This portfolio only shows public-safe proof. The strongest visible lane right now is June to July 2026: landing refactors, Scholarium surface-building, education packaging, and disciplined technical publication work.
Commit-linked
Client-safe proof
June-July 2026 verified
Recent delivery
Public evidence from the latest visible work cycle.
Each card below links to a public repository or a dated commit page that external reviewers can inspect directly.
SecuredMe root landing refactor
The root surface was rebuilt around education, docs, and pricing routes while keeping the public boundary explicit.
Scholarium theme and education branding
Public education tooling received branded theme assets and a cleaner SecuredMe Education framing.
Education docs shell
Documentation packaging for the education lane was pushed as a public shell rather than left as internal operator-only structure.
Education adapters and configuration work
Scholarium received adapter and configuration additions, showing system-level work beyond marketing copy.
Initial public Scholarium export
The education platform gained a public export trail, which matters because it proves the lane is more than an internal idea.
Surface one
Surface two
Neutrosophic software references
Neutrosophic Sets and Systems lists Jean-Sebastien Beaulieu contributions around AI decision systems, uncertainty semantics, and evidence-structured reasoning.
View NSS listing
Surface three
Technical white-paper writing
Public white-paper posts show the ability to turn complex AI ideas into structured explanatory material for external readers without flattening the technical content.
View AI education white paper post
Surface four
Scholarium public route
The root landing now hands off directly into the education product lane, which makes the portfolio relevant to a live public system instead of a disconnected archive.
Open ScholariumBooks and long-form research
Co-author support for serious books, research manuscripts, and expert knowledge.
This lane is for professors, founders, researchers, and domain experts who have the ideas, notes, voice, and lived expertise, but need a disciplined partner to turn the material into a coherent book.
From scattered expertise to a controlled book package
I help transform long conversations, source files, chapter fragments, multilingual notes, diagrams, and research claims into a manuscript that has structure, authorship boundaries, review checkpoints, and a clean delivery trail.
- Book architecture, chapter map, and contribution boundaries.
- Research synthesis, source discipline, and claim review.
- French, English, and Spanish edition planning when needed.
- Cover direction, appendices, controlled review packets, and publication handoff.
Book diagnosis
Map the idea, audience, source base, authorship model, chapter structure, risks, and missing materials before anyone promises a manuscript.
Co-author architecture
Separate who contributes what: author voice, scientific review, translation, preface, chapter ownership, validation, and final publication responsibility.
Research-to-manuscript build
Turn notes, interviews, emails, lectures, PDFs, datasets, and technical claims into readable chapters with careful boundaries and source memory.
Controlled delivery
Prepare review packets, versioned files, summaries, publication assets, and final delivery gates so the project stays professional and traceable.
Best fit: complex nonfiction, research books, technical books, memoir-with-method, education methods, AI/science manuscripts, and bilingual or trilingual publication projects. Not a vanity-publishing promise, not legal representation, and not a guarantee of publisher acceptance.
Client review mode
What can be shown in a serious call
The goal is not to flood the call with artifacts. It is to show the proof that matches the buyer’s constraint.
Repository walkthrough
Recent GitHub work, commit history, route structure, validation scripts, and the implementation logic behind the page.
Education platform route
Scholarium positioning, branded shell work, adapters, and the handoff between public landing and education product.
Technical paper sample
Executive thesis, claims table, explanation discipline, and source-aware writing that stays readable.
System diagnostic map
Decision points, uncertainty sources, contradiction handling, and the execution sequence required to ship.
Next step
Need proof closer to your use case?
SecuredMe can curate a tighter walkthrough from the public record and then move into a bounded diagnostic or implementation lane.