Repository navigation
Karma points are awarded by the Simon Contribution Recorder - #1194
Merged
Merged
Conversation
Signed-off-by: Mandy Chessell <mandy.e.chessell@gmail.com>
mandy-chessell
enabled auto-merge
October 30, 2026 15:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Karma points documentation for the Simon Contribution Recorder
Summary
In 6.3, karma points are awarded by a new nanny integration connector, the Simon Contribution Recorder, instead of the Award Karma Points Lovelace watchdog service (odpi/egeria PR to follow). This PR updates the pages that describe karma points, adds the 6.3 release notes, and regenerates the mermaid graphs that still showed the karma service.
Pages
concepts/karma-point.md- rewritten: Simon awards the points from the Core Content Pack's OpenMetadataObservability group, one per change, written on each refresh (12 minutes by default); the actor profile requirement; and a new People and automation section onignoredUserIdPatterns, which by default (.*npa,.*engine) awards points to people only. The page used to say automation earns points.egeria-solutions/organization-insight/overview.md- How points are awarded rewritten, with a table of what happens in each situation and its audit log message (SIMON-CONTRIBUTION-RECORDER-0003to-0007); points are added to the stored total; changes made while Simon is not running earn nothing; run Simon only once per set of repositories; why content pack loads produce discarded points for "Egeria Project". The karma engine action graph is removed, and the introduction no longer says that all of Organization Insight comes from the Lovelace services.features/metadata-observability/overview.md- Simon added to Figure 1 and the introduction, with a new The Simon Contribution Recorder section after Pepys; the karma row removed from the Lovelace services table; the operational view table and the set-up list name Simon.features/people-roles-organizations/overview.mdandtypes/1/0125-Contribution.md- name Simon and the people-only default; the type page gives the qualifiedName and displayName of the records Simon creates.guides/developer/watchdog-action-services/overview.md- the worked example was the karma service. The code samples now use an illustrativeChangeWatchdogService, and the examples list says Egeria currently supplies no watchdog action service, linking the karma service's source at tagV6.2.Corrections found on the way
isPublicis not a property of ContributionRecord (the type has onlykarmaPoints, and the 0125 diagram already agreed). Removed from the concept, type and Organization Insight pages; the Organization Insight page now says visibility follows the security of the actor profile.Release notes (
snippets/release-notes/6-3.md)simonnpato theintegrationConnectorgroup of your own user directory; automation no longer earns karma points by default; the karma definitions are soft-deleted on upgrade and the EgeriaWatchdog engine has no services; the new PostgreSQL indexes are built on first start, or can be built beforehand withCREATE INDEX CONCURRENTLYunder the same names.Mermaid snippets
Regenerated from a platform running the new content packs, using the same logic as
extract-mermaid-graphs.ipynb:award-karma-pointssnippets, and theegeria-observability-content-packandjacquard-harvester-content-packgraphs, whose blueprints no longer exist. None of them was included by any page.Testing
mkdocs buildsucceeds with no new warnings; the new anchors (#the-simon-contribution-recorder,#how-points-are-awarded,#people-and-automation) render.🤖 Generated with Claude Code