BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//OpenTeams | AI you own - ECPv6.18.2//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-ORIGINAL-URL:https://openteams.com
X-WR-CALDESC:Events for OpenTeams | AI you own
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-Robots-Tag:noindex
X-PUBLISHED-TTL:PT1H
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:UTC
DTSTART:20250101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=UTC:20260820T120000
DTEND;TZID=UTC:20260820T130000
DTSTAMP:20260813T141150Z
CREATED:20260807T173852Z
LAST-MODIFIED:20260813T141150Z
UID:35830-1787227200-1787230800@openteams.com
SUMMARY:Ungating the Supply Chain: The Future of Artifact Security
DESCRIPTION:Every piece of software you ship is a recipe. The ingredients (libraries\, containers\, packages) are artifacts\, and so is the finished product you deliver to customers. Now imagine the platforms managing your pantry charge extra to tell you whether your ingredients are contaminated. That’s the state of commercial artifact management today: vulnerability scanning\, artifact signing\, and access controls are locked behind enterprise tiers costing tens of thousands of dollars per year. Security has become a luxury good\, and the teams who can least afford it go without. \nThis talk tells the story of Artifact Keeper\, a fully open-source\, MIT-licensed artifact management platform where every feature ships free: integrated vulnerability scanning\, 45+ package formats\, artifact signing\, SBOM generation\, SSO\, and built-in migration tooling. No open-core gimmicks\, no gated “community edition.” \nWe will also take a quick behind-the-scenes look at how the platform was built in 6 months\, largely by one engineer\, with AI-assisted development playing a major role: where it genuinely accelerated the work\, where it confidently failed\, and how to catch it. A live demo shows the real platform running\, from deployment to a vulnerability scan. \nAttendees will leave with: \n\na plain-language understanding of artifact management and why software supply chain security matters to every team\, not just enterprises\,\na clear picture of the real threats: dependency confusion\, typosquatting\, compromised packages\, and unsigned artifacts\,\nan honest comparison of Artifact Keeper against commercial platforms and where each fits\,\na practical walkthrough for standing up a secure artifact registry with vulnerability scanning and policy filters in a dev environment.\n\n\nREGISTER VIA ZOOM \nAbout the Speaker \nBrandon Geraci is a Senior Software/Infrastructure Engineer at OpenTeams based in Austin\, Texas\, where he works on open source AI and DoD infrastructure\, including Nebari deployments on Kubernetes and AI/ML platform engineering. He is the creator of Artifact Keeper\, a fully open source\, MIT-licensed artifact management platform.\nHis open source journey began at age 12\, piecing together outdated hardware and running Linux to squeeze the most out of it. A combat veteran with 8 years in the US Army\, he understands firsthand how critical reliable and verifiable artifacts are when deploying solutions customers depend on. He holds a Master’s in Computer Science from the University of Minnesota Duluth and believes open source will make our world more secure. \nAbout the Open Source Architect Community \nThe Open Source Architect (OSA) Community is an invitation-only group for seasoned software architects who are passionate about open source technology. Request to join the OSA Community: https://forms.gle/7efbynVzYhhH2LCQ7\nWe review each application carefully. If it’s a fit\, you’ll get an invite to join the space where it all happens.\nFor the latest updates on all things open source\, follow our public feed on LinkedIn.
URL:https://openteams.com/event/ungating-the-supply-chain-the-future-of-artifact-security/
ATTACH;FMTTYPE=image/png:https://openteams.com/wp-content/uploads/2026/08/OSAC-August-26-Webinar.png
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=UTC:20261015T120000
DTEND;TZID=UTC:20261015T130000
DTSTAMP:20261009T190959Z
CREATED:20261008T130736Z
LAST-MODIFIED:20261009T190959Z
UID:43839-1792065600-1792069200@openteams.com
SUMMARY:Evidence\, Attestation\, and Requirements Traceability with Python and Flexo MMS
DESCRIPTION:Reproducibility tells you a computation can be re-run. It does not tell you the result justifies the claim you are making with it. Between the two sits a layer our tooling rarely captures: the assumptions a model rests on\, the provenance chain from source to artifact\, and the judgment that this evidence is sufficient. Today those live in notebook text\, docstrings\, and chat threads. They are unversioned\, non-queryable\, and first to rot. \nEngineering disciplines that carry legal accountability have a structure for this\, and it generalizes cleanly to scientific software. Three linked layers: requirements are the claims you commit to\, evidence is what your code produces\, and attestation is a named person judging the model adequate and the evidence sufficient. The value here is not the paperwork; it is that all three become queryable data. \nThe implementation is a knowledge graph. RDF lets the vocabulary come from standards that already exist: PROV for provenance\, EARL for outcomes\, SHACL for the rules that must be satisfied. This approach makes correct construction suitable for CI/CD work flows and turns review into a query. What assumptions does this result depend on? What conclusions break if this analysis changes? Who signed off\, and against which version? \nGraphs like this need version control\, which is where OpenMBEE Flexo MMS  comes in: a branchable RDF store that gives engineering artifacts the commit\, branch\, and diff semantics Git gives code. \nThe talk works end to end in Python on a satellite attitude-control system: SymPy proofs\, SciPy simulations\, digest-pinned containers\, hashed evidence\, attestations bound into named graphs\, provenance pushed live to Flexo. It closes on the boundary that makes the rest trustworthy — automation verifies claims within a model; only a person can attest that the model was adequate. While the example comes from aerospace\, the same discipline can be applied to Machine Learning models and AI workflows; or any other system sensitive modeling assumptions that are used to inform or make decisions. \n\nREGISTER VIA ZOOM \nAbout the Speaker \nMichael Zargham is CEO and Chief Engineer of Dynamical Systems Group\, a systems engineering firm that helps high-reliability organizations put emerging technology to dependable use across civil and commercial aerospace\, public-sector R&D\, and the open infrastructure that science and engineering depend on. \nWithin OpenMBEE\, he helps set technical roadmap and ecosystem direction\, with contributions centered on knowledge enforcing traceability discipline across the lifecycle of model-based systems engineering artifacts. \nThe through-line in his work is one design discipline: simple local algorithms with provable relationships to desirable global properties\, under the weakest possible assumptions about agent behavior. The mathematics is the same whether the agents are robots\, markets\, or institutions. \nHe holds a Ph.D. in Electrical and Systems Engineering from the University of Pennsylvania in optimization and control of distributed systems\, has taught at Penn and Carnegie Mellon\, and serves on the NumFOCUS Advisory Council. \nAbout the Open Source Architect Community \nThe Open Source Architect (OSA) Community is an invitation-only group for seasoned software architects who are passionate about open source technology. Request to join the OSA Community: https://forms.gle/7efbynVzYhhH2LCQ7\nWe review each application carefully. If it’s a fit\, you’ll get an invite to join the space where it all happens.\nFor the latest updates on all things open source\, follow our public feed on LinkedIn.
URL:https://openteams.com/event/evidence-attestation-and-requirements-traceability-with-python-and-flexo-mms/
ATTACH;FMTTYPE=image/png:https://openteams.com/wp-content/uploads/2026/10/Website-Announcement-1.png
END:VEVENT
END:VCALENDAR