Maintain a since_version column on every row and a release_history field with introduction, modification, and deprecation events. SleekRank can render a release-grouped index at /linux/syscalls/by-version/{kernel}/ from the same data. Readers writing code for kernel 5.10 LTS see exactly which calls are available without grepping git logs, and the dateModified field updates with every edit.

Yes. The archs JSON array on each row lists every architecture that ships the syscall. A list mapping renders arch badges and feeds /linux/syscalls/by-arch/{arch}/ index pages. Architecture-only syscalls like arch_prctl on x86 or mmap2 on legacy 32-bit ARM carry a clear badge so cross-platform code authors avoid surprises during builds.

Add an errnos_arch_specific JSON object keyed by arch with an array of errno values per architecture. A conditional list mapping renders an arch-specific errno block when the data is present. Otherwise the page uses the canonical errno list. Most syscalls do not need this, but for the handful where it matters (older mips/sparc edge cases), the data is right there.

Add a wraps and superseded_by column. A relationship block on each page renders the syscall family tree. The openat2 page links back to openat and forward to any future variant. Readers porting code see the modernization path with one click, and search engines pick up the related TechArticle relationships as JSON-LD for rich result eligibility.

Yes. Add a vdso_accelerated boolean and a vdso_arch JSON object detailing which architectures route the call through the vDSO. A badge on each page shows the optimization, and the index can filter to vDSO-accelerated calls only. Performance-sensitive readers see the difference between a real syscall trap and a vDSO call without reading kernel source.

Each page carries a unique signature, unique errno list, unique parameter table, unique example C code, and unique kernel history. That is more structured data per page than most kernel reference sites publish. Search behavior matches MDN web reference pages, which rank reliably because every entry is genuinely unique and updated when the underlying API ships a new revision.

Yes. A capabilities JSON array on each row lists CAP_NET_ADMIN, CAP_SYS_ADMIN, and similar requirements. A list mapping renders a capabilities badge strip on every page. seccomp-related notes go into a separate text column so security tool builders writing seccomp filters see exactly which calls need which privileges before allowlisting.

Flip the deprecated_since_version field and add a deprecation_reason note. The page renders a deprecation banner with the replacement syscall linked. The sitemap keeps the URL alive so external code references that point to it still resolve. Search engines see the dateModified update and reindex with the deprecation context surfaced in the title and description.