Add WikiEntryProposal validator

[keepsloading]

Goal

Add a contract validator for app-proposed Wiki entries.

Apps should be able to propose readable context, but the proposal shape needs to be consistent before Wiki, Memory, SDK, and Access can rely on it.

Suggested fields

A Wiki entry proposal may include:

• proposal id
• source app id
• category
• title
• body
• confidence
• evidence references
• suggested visibility
• suggested permissions
• created timestamp

Work to do

• Define the WikiEntryProposal shape
• Add a validator following the existing Contracts style
• Return { ok: true, value } for valid input
• Return { ok: false, errors: [{ path, message }] } for invalid input
• Add valid examples
• Add invalid examples
• Export the validator from the package

Important product rule

Apps propose context. Users decide whether it becomes accepted memory.

Acceptance criteria

• Valid Wiki entry proposals pass
• Missing required fields fail with useful errors
• Invalid field types fail with useful errors
• The validator is documented in the README or examples

---

SSoC26 Contributor Notice:

Since this repository (Memact/Contracts) is outside the main Context repository, and the registered project for tracking contributions is specifically Context (Memact/Context), please make sure to create a dummy PR in the Context repository linking to your actual PR or commits in this repository. This is required for your contribution to be correctly tracked and counted.

If you have already created a dummy PR in Memact/Context linking to your work here, please ignore this message!

[kir943]

Hi @keepsloading,

I would like to work on this issue under SSOC'26.

I have reviewed the requirements and understand that the goal is to create a robust validator for WikiEntryProposal that ensures proposed wiki entries follow a consistent contract before being consumed by Wiki, Memory, SDK, and Access components.

My implementation plan is:

1.Define the WikiEntryProposal schema according to the suggested fields.
2.Implement a validator following the existing Contracts package conventions.
3.Return standardized validation responses for both valid and invalid inputs.
4.Add comprehensive valid and invalid test cases.
5.Provide clear error messages for missing or incorrectly typed fields.
6.Export the validator from the package and document its usage with examples.

I have experience working with TypeScript, validation logic, APIs, and structured data contracts, and I am confident I can deliver a clean and well-tested implementation.

Could you please assign this issue to me?

Thank you!

[keepsloading]

@kir943 maintainer assignment: this issue is yours for SSoC26. This is one of your two active Memact issues.

Your validator plan is aligned: define WikiEntryProposal, follow the existing Contracts validation style, add valid and invalid tests, export it, and include a small example. Keep the first PR focused on this validator only.

[keepsloading]

Alignment Update: Under the V1 architecture, we use the terms 'Notebook' and 'Suggestions' instead of 'Wiki entries' and 'Wiki proposals'. The validator should define and validate SuggestionProposal instead of WikiEntryProposal, checking suggestion fields (e.g. suggestion_id, source_app_id, category, title, body, visibility, etc.). Please implement the validator matching this naming convention.

[relda88]

Hit this same issue — the root cause was the missing null check before deserialization. Wrapping in a try/catch fixed it on our end.

[keepsloading]

Attention @kir943:

Maintainer Notice regarding SSoC26 contributions:

Since this repository (Memact/Contracts) is outside the main Context repository, and the registered project for tracking contributions is specifically Context (Memact/Context), please make sure to create a dummy PR in the Context repository linking to your actual PR or commits in this repository. This is required for your contribution to be correctly tracked and counted.

If you have already created a dummy PR in Memact/Context linking to your work here, please ignore this message!

[keepsloading]

Hi @kir943! As part of Memact's V1 architectural changes, we are phasing out 'Wiki entry' and 'Wiki' terminology in favor of 'Claims' and 'Context Suggestions'. For this validator implementation, please rename/update the classes and interfaces (e.g. changing WikiEntryProposal to ContextSuggestionProposal or similar suggestion validation structures) to fit with the new V1 design.

[keepsloading]

Hi @kir943 👋 Just checking in on this issue! It has been assigned to you for over 3 days. Are you still working on it, or do you need any help? If you're no longer able to work on it, please let us know so we can unassign you and keep the backlog moving. Thanks for contributing!