[Submission] Faldony — self-hosted document archive with durable processing #129

Activity

1. SixthPhilosopher

   added

   code exchange submissionCode and/or content about Temporal!Code and/or content about Temporal!

   triageIssues that Temporal folk need to look atIssues that Temporal folk need to look at

   on Sep 6, 2026
2. github-actions commented on Sep 6, 2026

   

   github-actionsBot

   on Sep 6, 2026 – with GitHub Actions

   Last edited by github-actions

   More actions

   ZiggyBot — automated pre-evaluation

   ---

   Criterion	Assessment
   Useful to Temporal users	✅ Yes — Demonstrates durable ingestion pipelines, Saga compensation, cooperative cancellation, and Workflow Streams as a reference implementation in the Java SDK.
   Benefits clearly explained	✅ Yes — The README and submission describe the problem, architecture, and Temporal usage in specific technical detail.
   OSI Approved License	✅ Yes — GPL-3.0 is OSI-approved and present in the repository.
   README with working instructions	⚠️ Unclear — The README covers architecture and design extensively, but the setup/deployment instructions fall in the truncated tail and cannot be verified from the available content.

   Overall: Needs review ⚠️

   Notes:

   • Language declared as Java in the submission, but the source is Kotlin on the JVM using the Temporal Java SDK; the submission text refers to "Java SDK" while the code path is .../kotlin/.... Minor labeling inconsistency, not a defect.
   • The stated language field ("Java") conflicts with the KMP/Kotlin badges and .kt source files; worth confirming for catalog accuracy.
   • Temporal usage is non-trivial and covers multiple primitives: per-document workflows keyed by content hash, Saga compensation in a detached cancellation scope, cooperative cancellation via signal plus requestCancel, heartbeat-based batch resumption, a reconciliation Schedule, and Workflow Streams bridged to SSE.
   • The claim that Temporal open-workflow visibility is ephemeral, motivating a durable projection into a processing_ledger, is a reasonable design decision and is documented.
   • Single-write finalize activity establishing a "row exists == fully processed" invariant is a clean idempotency boundary; it depends on the finalize activity being idempotent under retry, which is asserted but not verifiable from the truncated files.
   • Repository has 0 stars and is marked beta; arm64/Raspberry Pi target is stated as not yet validated.
   • DocumentProcessingWorkflow.kt is truncated at the review boundary; the compensation and cancellation logic described in the docstring could not be fully inspected in the workflow body.

   Suggested questions for submitter:

   • Confirm the primary implementation language for the catalog entry (Kotlin vs. Java).
   • Do the README setup instructions include a complete, runnable docker-compose quickstart, and have they been validated on a clean environment?
   • Are the finalizeDocument and embedMissingChunks activities idempotent under retry, and is the single-write finalize transactional across the document row and all chunk rows?

   Notable Temporal pattern:

   Saga compensation executed inside a detached cancellation scope combined with cooperative cancellation (signal plus requestCancel rather than terminate), ensuring cleanup activities run even when the root scope is cancelled. This is representative because it addresses a specific Temporal gotcha where a cancelled root scope would otherwise cancel the compensation activities before they execute.
   View in source ↗

   ---

   Automated AI pre-screen by ZiggyBot. Final decisions are made by the community team.

   Reviewer: Check the box below to generate a Contentful-ready long description for this submission.

   • Generate long description if needed
3. github-actions commented on Sep 6, 2026

   

   github-actionsBot

   on Sep 6, 2026 – with GitHub Actions

   More actions

   ZiggyBot — automated pre-evaluation

   An error occurred during automated evaluation; the community team will need to review this submission manually.

   401 {"type":"error","error":{"type":"authentication_error","message":"API key is invalid."},"request_id":null}
   

   ---

   Automated AI pre-screen by ZiggyBot. Final decisions are made by the community team.
4. SixthPhilosopher commented on Sep 8, 2026

   

   SixthPhilosopher

   on Sep 8, 2026

   Author

   More actions

   Hi! Just following up on this submission to check whether it’s in the review queue.

   It looks like the automated pre-evaluation has failed twice with an authentication error (401 API key is invalid). I’m not sure if that means the submission is waiting for manual review, or if it may have been missed by the process pipeline.

   Could someone confirm whether the submission is still queued for review?

   Thanks!
5. Shy commented on Sep 17, 2026

   

   Shy

   on Sep 17, 2026

   Member

   More actions

   Thanks for catching. I'm working with our IT team to get our key fixed.
6. Shy

   self-assigned this

   on Sep 17, 2026
7. github-actions

   added

   ziggy reviewedPre-screened by ZiggyBotPre-screened by ZiggyBot

   on Sep 17, 2026
8. Shy

   assigned

   karasowles

   and unassigned

   Shy

   on Oct 8, 2026
9. Shy

   added

   website ready!This is ready to be added to the Code Exchange site by a TemporaliteThis is ready to be added to the Code Exchange site by a Temporalite

   and removed

   triageIssues that Temporal folk need to look atIssues that Temporal folk need to look at

   on Oct 8, 2026